CVE-2021-3808
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 · uneditedPotential security vulnerabilities have been identified in the BIOS (UEFI Firmware) for certain HP PC products, which might allow arbitrary code execution. HP is releasing firmware updates to mitigate these potential vulnerabilities.
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 · low confidenceVulnerability in HP PC BIOS (UEFI Firmware) allows arbitrary code execution. The specific vulnerability type and technical details are not disclosed in available documentation. This is a firmware-level flaw affecting certain HP systems.
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= 01.12.00= 1.41= 01.19.00= 01.12.00= 1.41= 01.19.00= 1.4= 01.20.00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your HP system modelRun `wmic csproduct get name` on Windows or `dmidecode -s system-product-name` on Linux to get the exact model nameAffected if The model is not one of: Elite Dragonfly, Elite X2 1012 G2, Elite X2 1013 G3, Elite X2 G4, Elitebook 1040 G4, Elitebook 1050 G1, Elitebook 725 G4, Elite Elitebook 735 G5 (not affected)
-
Retrieve the current BIOS versionOn Windows, run `wmic bios get smbiosbiosversion` or check via BIOS setup (F10 at startup). On Linux, run `dmidecode -s bios-version`Affected if No version can be retrieved or BIOS is not accessible for inspection
-
Compare your BIOS version to affected listCheck the version you retrieved against the affected versions: Elite Dragonfly = 01.12.00, Elite X2 1012 G2 = 1.41, Elite X2 1013 G3 = 01.19.00, Elite X2 G4 = 01.12.00, Elitebook 1040 G4 = 1.41, Elitebook 1050 G1 = 01.19.00, Elitebook 725 G4 = 1.4, Elitebook 735 G5 = 01.20.00Affected if Your BIOS version matches exactly one of these listed versions (version equals sign indicates exact version match)
-
Confirm firmware is the HP UEFI BIOSVerify the BIOS vendor is HP by running `wmic bios get manufacturer` on Windows or checking the BIOS setup screen at startupAffected if The BIOS is not from HP (not affected)
You are affected only if your system is one of the eight listed HP models AND your current BIOS version matches exactly the version specified for that model in the affected products list.
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 HP-supplied BIOS/UEFI firmware updates to affected systems. Verify the current BIOS version on each system and cross-reference with HP's affected product list before updating.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3808 — 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-2021-3808 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