Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-13980

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

H3C IMC contains an unauthenticated remote command execution vulnerability in the /byod/index.xhtml endpoint. Attackers can exploit improper JSF ViewState handling by crafting POST requests with forged javax.faces.ViewState parameters, achieving arbitrary command execution without authentication or session cookies.

MitigationApply vendor patch when available; as interim measures, disable or restrict access to the /byod endpoint, implement WAF rules blocking malicious ViewState payloads, and segment affected systems from untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if H3C IMC is present
    Check your inventory or running services for H3C IMC (also known as H3C Intelligent Management Center). Look for processes listening on common IMC ports (typically 8080, 8443, or 443) or check for IMC web application files on the system.
    Affected if H3C IMC software is installed and running on the system
  2. Determine the installed IMC version
    Access the IMC web interface and look for version information usually found in the About page, help menu, or footer. Alternatively, check version files in the IMC installation directory if accessible.
    Affected if The installed version is E0632H07 or any version lower than E0632H07 (the summary indicates versions up to E0632H07 are affected)
  3. Verify if /byod endpoint is accessible
    Send an HTTP GET request to https://<imc-host>/byod/index.xhtml (or http if HTTP is used). Check if the page loads or responds with a 200 OK status.
    Affected if The /byod/index.xhtml endpoint responds and is reachable from the network
  4. Confirm network exposure of IMC management interface
    Review firewall rules, access control lists, or network segmentation to determine if the IMC web interface (port 8080, 8443, or 443) is exposed to untrusted networks or the internet.
    Affected if The IMC management interface is directly accessible from untrusted networks without VPN or firewall restriction

A system is affected if H3C IMC version E0632H07 or lower is installed and the /byod/index.xhtml endpoint is network-accessible, allowing unauthenticated attackers to exploit the ViewState parameter forgery for remote command execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; as interim measures, disable or restrict access to the /byod endpoint, implement WAF rules blocking malicious ViewState payloads, and segment affected systems from untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13980 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data