dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-0077

HIGH · 7.8 CVSS v3.1 Published 2024-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Virtual GPU Manager contains a vulnerability in the vGPU plugin, where it allows a guest OS to allocate resources for which the guest OS is not authorized. A successful exploit of this vulnerability may 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 confidence

NVIDIA Virtual GPU Manager's vGPU plugin contains an authorization bypass where a guest virtual machine can allocate GPU resources beyond what it is entitled to. This vulnerability allows an unprivileged or malicious guest OS to access resources outside its allocated vGPU profile, potentially leading to privilege escalation, information disclosure, or denial of service.

MitigationApply the NVIDIA Virtual GPU Manager security update (ensure vGPU software is updated to a version containing the fix). Review guest VM resource allocations and monitor for unauthorized resource access patterns.

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

CVSS:3.1/AV:L/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 if NVIDIA vGPU software is installed
    Check for Virtual GPU Manager components on the hypervisor host. On VMware ESXi, look for 'nvidia-vgpu' or 'NVIDIA-VMware' packages via 'esxcli software vib list | grep nvidia' or check the VMkernel logs for nvidia driver loading. On other hypervisors, check for nvidia driver/vgpu services.
    Affected if No NVIDIA vGPU software is found - not affected. If nvidia-vgpu components are present, proceed to version check.
  2. Determine Virtual GPU Manager version
    On VMware ESXi, run 'esxcli software vib list | grep -i nvidia' to list installed NVIDIA VIBs and their versions. On KVM, check '/usr/share/vgpu_unlock/' or the installed nvidia-vgpu-*.rpm/.deb package versions. Note the full version string.
    Affected if The installed version is not yet patched - continue to verify configuration. If already running a version released after the security patch, likely not affected.
  3. Verify vGPU plugin is enabled
    Check the hypervisor configuration for active vGPU profiles. On ESXi, review the VM configuration files (.vmx) for 'vgpu' or 'nvidia' related settings, or use 'vmware-vmx -g' on running VMs. On KVM, check libvirt domain XML for <hostdev> with 'nvidia' or vGPU assignment entries.
    Affected if No vGPU profiles are assigned to any guest VMs - the specific attack surface may be limited, but the vulnerable code may still be present in the installation.
  4. Review guest VM resource allocation limits
    Audit all guest VMs configured with vGPU resources. On ESXi, use 'vmware-vmx -l' or check the vSphere UI for assigned GPU profiles. Compare each VM's assigned profile against its entitled quota. Look for any VMs with mismatched or excessive GPU resource assignments.
    Affected if Guest VMs have GPU resources assigned via the vGPU plugin - the vulnerability is applicable. VMs with unprivileged or potentially malicious guest OS access to vGPU profiles are at higher risk.

Your environment is affected if NVIDIA Virtual GPU Manager is installed with an unpatched version and any guest VMs have vGPU resources allocated, allowing the guest OS to bypass GPU resource entitlements.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA Virtual GPU Manager security update (ensure vGPU software is updated to a version containing the fix). Review guest VM resource allocations and monitor for unauthorized resource access patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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