dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-42934

MEDIUM · 5.0 CVSS v3.1 Published 2024-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
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
OpenIPMI before 2.0.36 has an out-of-bounds array access (for authentication type) in the ipmi_sim simulator, resulting in denial of service or (with very low probability) authentication bypass or code execution.

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 · high confidence

OpenIPMI versions prior to 2.0.36 contain an out-of-bounds array access vulnerability in the ipmi_sim simulator component when handling authentication type values. This memory corruption issue in the simulator can cause denial of service, and has very low probability of leading to authentication bypass or arbitrary code execution.

MitigationUpgrade OpenIPMI to version 2.0.36 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the ipmi_sim simulator to reduce attack surface.

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Detect if OpenIPMI is installed
    Check for OpenIPMI package using the system package manager (e.g., rpm -qa | grep -i openipmi, dpkg -l | grep -i openipmi, or yum list installed openipmi) or look for ipmi_sim binary in common paths (/usr/sbin/ipmi_sim, /usr/bin/ipmi_sim)
    Affected if OpenIPMI or ipmi_sim binary is present on the system
  2. Identify installed OpenIPMI version
    Run 'ipmi_sim -v' or 'ipmi_sim --version' to display the version, or query via package manager (e.g., rpm -q openipmi, dpkg -s openipmi)
    Affected if version displayed is lower than 2.0.36
  3. Confirm ipmi_sim simulator component is in use
    Check if ipmi_sim process is running (ps aux | grep ipmi_sim) or if simulator is configured/enabled in /etc/ipmi/ipmi_sim.cfg or similar configuration file
    Affected if ipmi_sim simulator is actively running or configured as enabled
  4. Compare version against affected range
    Compare the installed version from step 2 against the vulnerable range: versions prior to 2.0.36 are affected
    Affected if installed version is prior to 2.0.36 (e.g., 2.0.35, 2.0.34, etc.)

System is affected if OpenIPMI with ipmi_sim simulator is installed, the installed version is lower than 2.0.36, and the simulator component is enabled or running.

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

Upgrade OpenIPMI to version 2.0.36 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the ipmi_sim simulator to reduce attack surface.

Recommended fix Moderate confidence

OpenIPMI 2.0.36 or later

  1. 1. Identify the current installed version of OpenIPMI using package manager or 'ipmi_sim --version'
  2. 2. If running a version before 2.0.36, obtain the updated OpenIPMI 2.0.36 or later release from the official source (sourceforge.net/projects/openipmi)
  3. 3. Backup current OpenIPMI configuration files, typically located in /etc/ipmi/ or /usr/local/etc/
  4. 4. Install the updated OpenIPMI package using your system's package manager or compile from source
  5. 5. Verify the new version is running using 'ipmi_sim --version'
  6. 6. Test the ipmi_sim simulator functionality to confirm the update was successful
  7. 7. Restart any services using OpenIPMI

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42934 — 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-42934 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