dbcve.org
Proliant Microserver Gen10 Plus FirmwareOperating system · Hpe

CVE-2021-29213

MEDIUM · 6.7 CVSS v3.1 Published 2021-11-01
Fix available
A fix is available. Upgrade to 2.52 or later.
See remediation →
69/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
A potential local bypass of security restrictions vulnerability has been identified in HPE ProLiant DL20 Gen10, HPE ProLiant ML30 Gen10, and HPE ProLiant MicroServer Gen10 Plus server's system ROMs prior to version 2.52. The vulnerability could be locally exploited to cause disclosure of sensitive information, denial of service (DoS), and/or compromise system integrity.

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

A local security bypass vulnerability in HPE ProLiant DL20 Gen10, ML30 Gen10, and MicroServer Gen10 Plus system ROMs prior to version 2.52 allows a local attacker to potentially disclose sensitive information, cause denial of service, or compromise system integrity by circumventing security restrictions.

MitigationUpgrade HPE ProLiant DL20 Gen10, ML30 Gen10, and MicroServer Gen10 Plus system ROMs to version 2.52 or later to remediate this vulnerability.

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
Proliant Microserver Gen10 Plus FirmwareOperating system
Affected:< 2.52
Proliant Ml30 Gen10 Server FirmwareOperating system
Affected:< 2.52
Proliant Dl20 Gen10 Server FirmwareOperating system
Affected:< 2.52

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

CVSS:3.1/AV:L/AC:L/PR:H/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. Confirm your server model
    Identify whether the system is an HPE ProLiant DL20 Gen10, ML30 Gen10, or MicroServer Gen10 Plus. Check the server label, BIOS startup screen, or iLO web interface for the exact model number.
    Affected if The server is not one of these three models, the check does not apply.
  2. Locate the iLO web interface
    Access the iLO web interface by entering the iLO IP address in a browser. Log in with administrative credentials. Navigate to the 'Information' or 'Overview' section to view system details.
    Affected if iLO is not accessible or credentials are unavailable - you cannot verify the firmware version through this method.
  3. Check the system ROM firmware version
    In the iLO web interface, look for the 'Firmware Version' or 'System ROM' field under the general system information. Record the exact version number displayed (for example, it may appear as '2.40' or '2.50').
    Affected if The firmware version field is not visible or not populated.
  4. Compare version against 2.52
    Take the version number shown (for example, '2.40', '2.30', '2.50') and compare it numerically to 2.52. Versions below 2.52 (such as 2.50, 2.40, 2.30) are affected. Version 2.52 or higher is not affected.
    Affected if The installed system ROM firmware version is less than 2.52, indicating the system is vulnerable to CVE-2021-29213.

Your system is affected if it is an HPE ProLiant DL20 Gen10, ML30 Gen10, or MicroServer Gen10 Plus with system ROM firmware version earlier than 2.52.

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

Upgrade HPE ProLiant DL20 Gen10, ML30 Gen10, and MicroServer Gen10 Plus system ROMs to version 2.52 or later to remediate this vulnerability.

Recommended fix High confidence

System ROM version 2.52

  1. Navigate to support.hpe.com and locate the firmware download section for your specific ProLiant server model (DL20 Gen10, ML30 Gen10, or MicroServer Gen10 Plus)
  2. Download the System ROM firmware version 2.52 or later for your server model
  3. Review the firmware update instructions provided by HPE (typically requires iLO access or USB-based update)
  4. Apply the firmware update following HPE's documented procedure, ensuring stable power throughout the process
  5. After reboot, verify the installed firmware version is 2.52 or higher
Caveat Firmware updates require careful handling; ensure stable power and follow HPE update procedures to avoid rendering the system unusable

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

Fix this in Proliant Microserver Gen10 Plus Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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