Elite Dragonfly FirmwareOperating system · Hp

CVE-2021-39299

HIGH · 8.8 CVSS v3.1 Published 2022-02-16
Fix available
A fix is available. Upgrade to 01.08.00 / 01.12.00 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click Patch available

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
Potential vulnerabilities have been identified in UEFI firmware (BIOS) for some PC products which may allow escalation of privilege and arbitrary code execution.

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

A detailed technical summary for this CVE is being prepared.

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
Elite Dragonfly FirmwareOperating system
Affected:< 01.12.00
Elite Dragonfly G2 FirmwareOperating system
Affected:< 01.08.00
Elite Dragonfly Max FirmwareOperating system
Affected:< 01.08.00
Elite X2 1013 G3 FirmwareOperating system
Affected:< 01.19.00
Elite X2 G4 FirmwareOperating system
Affected:< 01.12.00
Elite X2 G8 Tablet FirmwareOperating system
Affected:< 01.08.00
Elitebook 1050 G1 FirmwareOperating system
Affected:< 01.19.00
Elitebook 830 G5 FirmwareOperating system
Affected:< 01.19.00

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 01.08.00 / 01.12.00 / 01.19.00 or later
Fixed in 01.08.0001.12.0001.19.00
Vendor patch support.hp.com →
Recommended fix High confidence

Update UEFI BIOS to version 01.12.00 (Elite Dragonfly, Elite X2 G4), 01.08.00 (Elite Dragonfly G2/Max, Elite X2 G8), 01.19.00 (Elite X2 1013 G3, Elitebook 1050 G1, Elitebook 830 G5), or later as available from HP

  1. Navigate to HP Support: https://support.hp.com/us-en/document/ish_5661066-5661090-16
  2. Identify your exact HP notebook model from the affected products list (Elite Dragonfly, Elite Dragonfly G2, Elite Dragonfly Max, Elite X2 1013 G3, Elite X2 G4, Elite X2 G8 Tablet, Elitebook 1050 G1, or Elitebook 830 G5)
  3. Locate the BIOS/firmware update section for your specific product on HP's support website
  4. Download and install the BIOS update version that matches or exceeds: Elite Dragonfly: 01.12.00 | Elite Dragonfly G2: 01.08.00 | Elite Dragonfly Max: 01.08.00 | Elite X2 1013 G3: 01.19.00 | Elite X2 G4: 01.12.00 | Elite X2 G8 Tablet: 01.08.00 | Elitebook 1050 G1: 01.19.00 | Elitebook 830 G5: 01.19.00
  5. Reboot the system as prompted to complete the firmware update
Caveat Standard firmware update risks apply; ensure AC power is connected and do not interrupt the update process

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-39299 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