LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57482: H3C N12 V100R005 contains a buffer overflow vulnerability due to the lack of length verification in the 5G...

H3C N12 V100R005 contains a buffer overflow vulnerability due to the lack of length verification in the 5G wireless network processing function. Attackers who successfully exploit this vulnerability can cause the remote target device to crash or execute arbitrary commands by sending a POST request to /bin/webs.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-57482 is a critical buffer overflow in H3C N12 V100R005. A remote unauthenticated attacker may crash the device or run arbitrary commands through the device web service. Treat exposed devices as high priority, but the provided sources do not name a vendor patch or confirm active exploitation.

Executive priority

Prioritize this for rapid exposure review and containment. The business risk is highest where affected devices are internet-facing or manage sensitive network segments. Lack of confirmed active exploitation lowers certainty, not impact.

Technical view

The CVE describes CWE-120 in the 5G wireless network processing function caused by missing length verification. Exploitation is network-based with low complexity and no privileges or user interaction, targeting /bin/webs via POST. The CVSS 3.1 score is 9.8 with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to environments running H3C N12 V100R005, especially where the web management service is reachable from untrusted networks. The affected-products metadata is incomplete in the bundle, so inventory validation is essential.

Exploitation context

The CVE record says exploitation can crash the remote target or execute arbitrary commands. KEV is false in the provided bundle, and no cited source confirms active exploitation in the wild.

Researcher notes

The public record provides the weakness class, route, impact, and CVSS vector, but affected CPEs and remediation details are absent. Avoid assuming broader H3C product impact without vendor confirmation.

Mitigation direction

  • Identify H3C N12 devices and confirm any V100R005 firmware presence.
  • Restrict web management access to trusted administration networks only.
  • Block untrusted access to the affected web service path where feasible.
  • Check H3C or device supplier guidance for fixed firmware or official mitigation.
  • Prioritize replacement or isolation if no vendor fix is available.

Validation and detection

  • Inventory network devices for H3C N12 and firmware V100R005.
  • Confirm whether the web management service is exposed externally or broadly internally.
  • Review device and perimeter logs for crashes or suspicious POST activity to /bin/webs.
  • Track CVE and vendor references for patch, advisory, or exploitation updates.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-57482 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
2Source 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-57482Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.