CVE-2024-13980: H3C Intelligent Management Center (iMC) /byod/index.xhtml RCE
H3C Intelligent Management Center (IMC) versions up to and including E0632H07 contains a remote command execution vulnerability in the /byod/index.xhtml endpoint. Improper handling of JSF ViewState allows unauthenticated attackers to craft POST requests with forged javax.faces.ViewState parameters, potentially leading to arbitrary command execution. This flaw does not require authentication and may be exploited without session cookies. An affected version range is undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-08-28 UTC.
Security readout for executives and security teams
Plain-English summary
This is a critical unauthenticated remote command execution issue in H3C iMC. A reachable BYOD endpoint may let an attacker execute arbitrary commands without credentials or session cookies. For organizations using H3C iMC, the business risk is potential takeover of a network-management platform.
Executive priority
Treat this as urgent for any organization running H3C iMC. A network-management system compromise can affect visibility, configuration integrity, and downstream infrastructure trust. Internet-facing exposure should be addressed first while vendor guidance is confirmed.
Technical view
The flaw is described as improper JSF ViewState handling at /byod/index.xhtml, mapped to CWE-502. The bundle states attackers can craft POST requests with forged javax.faces.ViewState values, potentially causing command execution. Versions up to and including E0632H07 are named, but the affected range is otherwise undefined.
Likely exposure
Systems running H3C Intelligent Management Center with /byod/index.xhtml reachable from untrusted networks are the primary concern. Exposure is highest for internet-facing or broadly reachable management portals. The product/version data is incomplete, so inventory validation matters.
Exploitation context
Public exploit-tagged references exist in the bundle. The CVE is not marked KEV. The bundle reports exploitation evidence first observed by Shadowserver on 2024-08-28, but no direct Shadowserver URL is provided here, so current active exploitation is not independently confirmed from this bundle.
Researcher notes
Evidence is strong for vulnerability class and endpoint, but incomplete for exact version boundaries and remediation. Avoid assuming a patch name from this bundle. Public exploit-tagged references indicate reproducibility risk, so defensive validation should focus on inventory, exposure, and logs.
Mitigation direction
Identify all H3C iMC instances and versions, especially E0632H07 or earlier.
Restrict /byod/index.xhtml and management access to trusted administrative networks.
Check H3C PSIRT and vendor support channels for fixed versions or official mitigations.
Monitor logs for suspicious unauthenticated POST activity to /byod/index.xhtml.
Prioritize patching or compensating controls for externally reachable systems.
Validation and detection
Confirm whether H3C iMC is deployed and whether BYOD endpoints are enabled.
Review perimeter exposure for /byod/index.xhtml from untrusted networks.
Check product build/version against E0632H07 and vendor guidance.
Search application and proxy logs for unexpected POST requests to the endpoint.
Validate that management access controls block unauthenticated external reachability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-502 · source CWE mapping
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.