dbcve.org
BmcOperating system · Nvidia

CVE-2022-42284

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
57/100
Remediation priority · Elevated
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 BMC stores user passwords in an obfuscated form in a database accessible by the host. This may lead to a credentials exposure.

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 Baseboard Management Controller (BMC) firmware stores user passwords in an obfuscated (not cryptographically hashed) form in a database that the host operating system can access. An attacker with host-level access could potentially read the database and reverse the obfuscation to obtain valid user credentials.

MitigationApply the vendor-supplied NVIDIA BMC firmware update to remediate this vulnerability. Until then, restrict host access to the BMC database and monitor for unauthorized access attempts.

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
BmcOperating system
Affected:< 00.19.07

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
None
Availability
None

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

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 NVIDIA BMC firmware presence
    Determine if the system contains an NVIDIA Baseboard Management Controller. Check hardware inventory, BMC web interface, or IPMI device information.
    Affected if System uses NVIDIA BMC hardware
  2. Check BMC firmware version
    Retrieve the installed BMC firmware version via IPMI command (e.g., ipmitool -I lanplus -H <bmc_ip> -U admin -P password mc info) or through the BMC web interface. Compare the version number to the affected range.
    Affected if Firmware version is earlier than 00.19.07
  3. Verify host access to BMC database storage
    Examine whether the host operating system can access the BMC database or storage partition. Check mount points, filesystem paths, or network shares that may expose BMC data to the host.
    Affected if Host OS has read access to BMC database storage area
  4. Locate and inspect BMC credential database
    Search for the BMC user password database file on accessible storage. This may be located in /bmc, /var/bmc, or similar directories exposed to the host. Examine the file for stored password strings.
    Affected if Password database file exists and is readable from host
  5. Assess password storage format
    Examine the stored passwords in the database. Determine if they appear as obfuscated/encoded strings (reversible) rather than cryptographically hashed values (one-way).
    Affected if Passwords are stored in reversible obfuscated format rather than hashed

User is affected if their system has NVIDIA BMC firmware prior to version 00.19.07 AND the host OS can access the BMC credential database containing reversibly obfuscated passwords.

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 00.19.07 or later
Fixed in 00.19.07
Interim mitigation

Apply the vendor-supplied NVIDIA BMC firmware update to remediate this vulnerability. Until then, restrict host access to the BMC database and monitor for unauthorized access attempts.

Recommended fix High confidence

00.19.07 or later

  1. Identify the current NVIDIA BMC firmware version running on the affected system
  2. Navigate to the NVIDIA BMC firmware update section in the system management interface or download the firmware from NVIDIA's official support portal
  3. Download firmware version 00.19.07 or later from nvidia.custhelp.com
  4. Follow NVIDIA's standard firmware update procedure for BMC devices, which typically requires: a) Upload the firmware image through the BMC web interface or IPMI, b) Initiate the firmware update process, c) Allow the BMC to reboot and complete the update, d) Verify the new version is installed successfully

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

Fix this in Bmc 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-2022-42284 — 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-2022-42284 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