CVE-2024-0138
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 · uneditedNVIDIA Base Command Manager contains a missing authentication vulnerability in the CMDaemon component. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
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 confidenceNVIDIA Base Command Manager CMDaemon component lacks authentication controls, allowing unauthenticated remote attackers to interact with the daemon. This could enable code execution, privilege escalation, data tampering, information disclosure, or denial of service against the cluster management infrastructure.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if NVIDIA Base Command Manager is installedCheck for Base Command Manager installation directories such as /opt/nvidia/bcm, /usr/local/bcm, or look for bcm or cmd daemon processes using 'ps aux | grep -i cmd' or 'dpkg -l | grep nvidia' on Linux systemsAffected if NVIDIA Base Command Manager software is present on the system
-
Determine CMDaemon versionRun 'cmd --version' or check the daemon binary version directly - typically found at /opt/nvidia/bcm/bin/cmd or within the installation directory structure. Compare the version against any NVIDIA security bulletins for CVE-2024-0138Affected if CMDaemon version is unpatched and falls within the vulnerable release range
-
Verify CMDaemon is running and accessibleCheck if CMDaemon process is active using 'ps aux | grep cmd' and identify the listening port (default CMDaemon port is typically 8050). Use 'netstat -tlnp | grep 8050' or 'ss -tlnp | grep 8050' to confirm the daemon is bound to a network interfaceAffected if CMDaemon process is running and listening on a network interface
-
Assess network exposure of CMDaemonReview firewall rules and network configuration to determine if CMDaemon ports are accessible from untrusted networks. Check iptables,ufw, or cloud security groups for inbound rules allowing access to port 8050 or custom CMDaemon ports from external IPsAffected if CMDaemon ports are exposed to untrusted or public network segments without network access controls
A system is affected if NVIDIA Base Command Manager with an unpatched CMDaemon is installed, the daemon is running and network-accessible, and the environment lacks compensating network controls to restrict access.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the NVIDIA security patch for Base Command Manager immediately. If no patch is available, restrict network access to CMDaemon ports via firewall and implement monitoring for unauthorized daemon interactions.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0138 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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