CVE-2025-64123

9.8 CRITICAL

📋 TL;DR

This vulnerability in Nuvation Energy Multi-Stack Controller allows the device to act as an unintended proxy or intermediary, potentially bridging network boundaries that should remain separate. This affects all Multi-Stack Controller installations through version 2.5.1, potentially exposing internal networks to external threats.

💻 Affected Systems

Products:
  • Nuvation Energy Multi-Stack Controller (MSC)
Versions: through and including release 2.5.1
Operating Systems: Embedded/Proprietary
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments of affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could pivot through the controller to access protected internal networks, potentially compromising critical energy infrastructure systems.

🟠

Likely Case

Network segmentation bypass allowing unauthorized access to adjacent systems or data exfiltration through the controller.

🟢

If Mitigated

Limited to network boundary issues without direct system compromise if proper network controls are in place.

🌐 Internet-Facing: HIGH - If exposed to internet, could serve as entry point to internal networks.
🏢 Internal Only: MEDIUM - Could still bridge internal network segments, enabling lateral movement.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Network boundary bridging vulnerabilities typically require minimal technical skill to exploit once identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown - check vendor for updates beyond 2.5.1

Vendor Advisory: https://www.dragos.com/community/advisories/CVE-2025-64119

Restart Required: Yes

Instructions:

1. Contact Nuvation Energy for patch availability 2. Apply any available firmware updates 3. Restart the controller after patching

🔧 Temporary Workarounds

Network Segmentation Enforcement

all

Implement strict network segmentation to isolate the controller from sensitive networks

Access Control Lists

all

Apply firewall rules to restrict traffic through the controller

🧯 If You Can't Patch

  • Isolate the controller in a dedicated network segment with strict egress filtering
  • Implement network monitoring for unusual proxy-like traffic patterns

🔍 How to Verify

Check if Vulnerable:

Check controller firmware version via web interface or CLI

Check Version:

Check via controller web interface or contact vendor for CLI command

Verify Fix Applied:

Verify firmware version is above 2.5.1 and test network segmentation

📡 Detection & Monitoring

Log Indicators:

  • Unusual network traffic patterns
  • Unexpected proxy connections

Network Indicators:

  • Traffic bridging between network segments
  • Unexpected routing through controller

SIEM Query:

source_ip IN (controller_ip) AND dest_ip IN (protected_network) AND NOT expected_traffic

🔗 References

📤 Share & Export