Friday, April 4, 2025
HomeCVE/vulnerabilityHewlett Packard RCE Vulnerability Allows Attackers to Bypass Authentication and Execute Remote...

Hewlett Packard RCE Vulnerability Allows Attackers to Bypass Authentication and Execute Remote Commands

Published on

SIEM as a Service

Follow Us on Google News

A critical unauthenticated remote code execution (RCE) vulnerability in HPE Insight Cluster Management Utility (CMU) v8.2 allows attackers to bypass authentication and execute commands as root on high-performance computing (HPC) clusters, researchers revealed today.

Tracked as CVE-2024-13804, the flaw exposes HPC environments to full cluster compromise through weaponized Java client applications.

Anonymous access to the application
Anonymous access to the application

Technical Breakdown

The vulnerability stems from insecure client-side authorization controls in CMU’s Java Web Start (JNLP) application.

Opening the jar with JD-GUI
Opening the jar with JD-GUI

While the GUI client initially restricts administrative functions like cluster provisioning, threat actors can:

1. Decompile Critical JAR Components

Attackers reverse-engineered the cmugui_standalone.jar file using tools like JD-GUI, exposing client-side admin checks in the AdminUserModel.java class.

2. Forge Administrative Privileges

By modifying the isAdmin validation to always return true (shown below), attackers unlock restricted functions:

// Original code

public boolean isUserAdmin() { return this.isAdmin; } 

// Weaponized version

public boolean isUserAdmin() { return true; } 

3. Exploit RMI for Root Commands

The modified client leverages CMU’s Java Remote Method Invocation (RMI) on port 1099 to call the ExecuteCmdLine method, executing OS commands via:

java -jar weaponized_cmugui.jar

PoC attacks have demonstrated ifconfig and whoami execution with root privileges on cluster management nodes.

Saving decompiled source code
Saving decompiled source code

Attack Impact

Successful exploitation enables:
🟥 Full cluster control via management node access
🟥 Lateral movement to integrated iLO interfaces
🟥 Data theft/destruction in HPC environments

“Client-side authorization checks are security theater without server validation,” warned the researcher who discovered the flaw. “This lets attackers hijack cluster operations as root.”

Mitigation Challenges

HPE confirmed CMU v8.2 reached end-of-life (EOL) in Q4 2024, with no planned patches. Organizations must:

  1. Network-isolate CMU servers behind firewalls
  2. Block inbound traffic to port 1099/TCP
  3. Monitor for suspicious RMI connections

This flaw continues a pattern of RMI-related vulnerabilities in Java-based management tools:

YearCVEImpact
2021CVE-2021-44228Log4Shell RCE
2023CVE-2023-34050VMware Aria RCE
2025CVE-2024-13804HPE CMU Takeover

HPC operators are urged to accelerate migration to supported cluster managers and audit legacy CMU deployments immediately.

As one enterprise CISO noted: “Critical infrastructure tools hitting EOL without upgrade paths create ticking time bombs.”

Find this News Interesting! Follow us on Google NewsLinkedIn, and X to Get Instant Updates!

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Australian Pension Funds Hacked: Members Face Financial Losses

Several of Australia’s largest superannuation funds have been targeted in a coordinated cyberattack, leading...

Frida Penetration Testing Toolkit Updated with Advanced Threat Monitoring APIs

In a significant update to the popular dynamic instrumentation toolkit Frida, developers have introduced...

OpenVPN Flaw Allows Attackers Crash Servers and Run Remote Code

OpenVPN, a widely-used open-source virtual private network (VPN) software, has recently patched a security...

Apache Traffic Server Flaw Allows Request Smuggling Attacks

A critical vulnerability has been discovered in Apache Traffic Server (ATS), an open-source caching...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Australian Pension Funds Hacked: Members Face Financial Losses

Several of Australia’s largest superannuation funds have been targeted in a coordinated cyberattack, leading...

Frida Penetration Testing Toolkit Updated with Advanced Threat Monitoring APIs

In a significant update to the popular dynamic instrumentation toolkit Frida, developers have introduced...

OpenVPN Flaw Allows Attackers Crash Servers and Run Remote Code

OpenVPN, a widely-used open-source virtual private network (VPN) software, has recently patched a security...