dbcve.org
OnyxOperating system · Nvidia

CVE-2024-0104

HIGH · 8.8 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 3.10.4402 / 3.11.2002 or later.
See remediation →
94/100
Remediation priority · Urgent
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
NVIDIA Mellanox OS, ONYX, Skyway, MetroX-2 and MetroX-3 XC contain a vulnerability in the LDAP AAA component, where a user can cause improper access. A successful exploit of this vulnerability might lead to information disclosure, data tampering, and escalation of privileges.

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

This vulnerability exists in the LDAP AAA (Authentication, Authorization, and Accounting) component of NVIDIA Mellanox network OS products. A user can exploit improper access controls in the LDAP authentication implementation to potentially gain unauthorized access, escalate privileges, and access or modify sensitive data.

MitigationApply vendor-supplied firmware updates for affected products (Mellanox OS, ONYX, Skyway, MetroX-2, MetroX-3 XC). Review and harden LDAP configuration to ensure proper attribute mapping and group membership enforcement.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OnyxOperating system
Affected:< 3.10.4402
Mlnx OsOperating system
Affected:< 3.11.2002< 3.11.2202
Mlnx GwOperating system
Affected:< 8.2.2000
Nvda Os XcOperating system
Affected:< 18.2.2000

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify product and version
    Execute 'show version' or 'show system information' on the Mellanox switch CLI to retrieve the exact OS version and product model
    Affected if The running version falls below 3.10.4402 for Onyx, below 3.11.2002 or 3.11.2202 for MlnxOS, below 8.2.2000 for MlnxGW, or below 18.2.2000 for NvdaOS XC
  2. Verify LDAP AAA feature status
    Execute 'show ldap' or 'show aaa ldap' to check if LDAP authentication, authorization, or accounting is currently configured and enabled on the system
    Affected if LDAP AAA functionality is enabled and actively used for user authentication or authorization
  3. Check LDAP configuration for attribute mapping
    Review LDAP configuration settings using 'show ldap configuration' or 'show aaa ldap config' to inspect attribute mappings, group membership enforcement, and access control settings
    Affected if LDAP is configured with attribute mappings that may permit unauthorized access or improper privilege assignment based on the LDAP response handling
  4. Inspect LDAP server connection settings
    Examine LDAP server definitions via 'show ldap server' or equivalent command to identify configured directory servers and their bind settings
    Affected if The system is configured to connect to LDAP servers for authentication purposes

The environment is affected if the product version is below the specified thresholds AND LDAP AAA authentication is enabled, since the vulnerability resides specifically in the LDAP authentication implementation.

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
Upgrade available Upgrade to 3.10.4402 / 3.11.2002 / 3.11.2202 or later
Fixed in 3.10.44023.11.20023.11.2202
Interim mitigation

Apply vendor-supplied firmware updates for affected products (Mellanox OS, ONYX, Skyway, MetroX-2, MetroX-3 XC). Review and harden LDAP configuration to ensure proper attribute mapping and group membership enforcement.

Recommended fix High confidence

Onyx: >=3.10.4402 | MLNX OS: >=3.11.2002 or >=3.11.2202 | MLNX GW: >=8.2.2000 | NVIDIA OS XC: >=18.2.2000

  1. Identify the currently installed NVIDIA Mellanox product (Onyx, MLNX OS, MLNX GW, or NVIDIA OS XC)
  2. Determine the exact version number of the current installation using 'show version' or similar command
  3. For Onyx: Upgrade to version 3.10.4402 or later
  4. For MLNX OS: Upgrade to version 3.11.2002 or later, or 3.11.2202 or later
  5. For MLNX GW: Upgrade to version 8.2.2000 or later
  6. For NVIDIA OS XC: Upgrade to version 18.2.2000 or later
  7. After upgrade, verify the LDAP AAA configuration is intact and functioning properly
  8. Test LDAP authentication to ensure the fix does not impact legitimate access

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

Fix this in Onyx Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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