dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-46933

HIGH · 7.7 CVSS v3.1 Published 2025-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
An issue was discovered in Atos Eviden BullSequana XH2140 BMC before C4EM-125: OMF_C4E 101.05.0014. Some BullSequana XH products were shipped without proper hardware programming, leading to a potential denial-of-service with privileged access.

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

The Atos Eviden BullSequana XH2140 BMC ships with improper hardware programming in versions before C4EM-125: OMF_C4E 101.05.0014. This manufacturing defect allows authenticated privileged attackers to cause a denial-of-service condition on the BMC, likely through undefined hardware register states or uninitialized components that trigger failure when accessed with privileged commands.

MitigationApply BMC firmware update C4EM-125 (OMF_C4E 101.05.0014) or later to all affected BullSequana XH2140 systems. Restrict BMC administrative access to trusted personnel until the patch is applied.

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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
High

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

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. Confirm BullSequana XH2140 BMC model
    Access the BMC web interface, use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> mc info', or query the Redfish API endpoint /redfish/v1/Managers/1 to retrieve BMC model information
    Affected if The model is not BullSequana XH2140, as this CVE affects only that specific BMC hardware
  2. Retrieve BMC firmware version
    Check the BMC firmware version via the web interface firmware info page, or use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> mc info' to obtain the firmware version string
    Affected if Cannot retrieve a firmware version from the BMC, indicating potential inventory limitation
  3. Compare version against affected range
    Compare your installed firmware version string to C4EM-125: OMF_C4E 101.05.0014 - note the full version format includes both the build identifier (C4EM-125) and the release (OMF_C4E 101.05.0014)
    Affected if Your installed version is older than C4EM-125: OMF_C4E 101.05.0014 (for example, OMF_C4E 101.04.xxxx or earlier), meaning the improper hardware programming defect is present
  4. Verify attacker has BMC access
    Review BMC access logs, authentication records, and user account activity to determine if any authenticated privileged session existed
    Affected if An authenticated privileged user account was compromised or used, as this CVE requires authenticated privileged access to trigger the denial-of-service condition

A user is affected if they have a BullSequana XH2140 BMC running firmware version earlier than C4EM-125: OMF_C4E 101.05.0014 and the BMC is accessible to authenticated privileged attackers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply BMC firmware update C4EM-125 (OMF_C4E 101.05.0014) or later to all affected BullSequana XH2140 systems. Restrict BMC administrative access to trusted personnel until the patch is applied.

Recommended fix Moderate confidence

C4EM-125 (OMF_C4E 101.05.0014)

  1. 1. Identify the current BMC firmware version installed on the BullSequana XH2140 system
  2. 2. Navigate to the Atos Eviden support portal (support.bull.com) or eviden.com to obtain the C4EM-125 firmware (OMF_C4E 101.05.0014)
  3. 3. Review the firmware release notes for any specific update instructions or prerequisites
  4. 4. Apply the firmware update following the vendor's documented BMC firmware upgrade procedure
  5. 5. Verify the firmware version has been successfully updated to C4EM-125 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-46933 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