dbcve.org
Dragonfly Folio G3 2 In 1 FirmwareOperating system · Hp

CVE-2022-27538

HIGH · 7.0 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 01.03.01 / 01.04.00 or later.
See remediation →
72/100
Remediation priority · Elevated
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
A potential Time-of-Check to Time-of-Use (TOCTOU) vulnerability has been identified in the BIOS for certain HP PC products which may allow arbitrary code execution, denial of service, and information disclosure. HP is releasing BIOS updates to mitigate the potential vulnerability.

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
Dragonfly Folio G3 2 In 1 FirmwareOperating system
Affected:< 01.03.01
Elite Dragonfly FirmwareOperating system
Affected:< 01.22.00
Elite Dragonfly G3 FirmwareOperating system
Affected:< 01.04.00
Elite Dragonfly G2 FirmwareOperating system
Affected:< 01.11.00
Elite Dragonfly Max FirmwareOperating system
Affected:< 01.11.00
Elite X2 1013 G3 FirmwareOperating system
Affected:< 01.22.00
Elite X2 G4 FirmwareOperating system
Affected:< 01.22.00
Elite X2 G8 Tablet FirmwareOperating system
Affected:< 01.11.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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.03.01 / 01.04.00 / 01.11.00 or later
Fixed in 01.03.0101.04.0001.11.00
Vendor patch support.hp.com →
Recommended fix High confidence

Upgrade to BIOS/firmware version 01.03.01 (Dragonfly Folio G3), 01.22.00 (Elite Dragonfly, Elite X2 1013 G3, Elite X2 G4), 01.04.00 (Elite Dragonfly G3), or 01.11.00 (Elite Dragonfly G2/Max, Elite X2 G8 Tablet)

  1. 1. Identify the exact HP model number and current BIOS/firmware version of the affected system
  2. 2. Visit the HP support page at https://support.hp.com/us-en/document/ish_7387020-7387107-16/hpsbhf03827 or search for the specific model on support.hp.com
  3. 3. Download the appropriate BIOS/firmware update for the specific model from HP's support website
  4. 4. Follow HP's instructions to update the BIOS - this typically involves running the HP BIOS Update utility or flashing the BIOS from within the operating system
  5. 5. Ensure the system is connected to AC power during the update process and do not interrupt the update
  6. 6. After the update completes, verify the BIOS version matches the fixed version (01.03.01 for Dragonfly Folio G3, 01.22.00 for Elite Dragonfly and Elite X2 1013 G3/G4, 01.04.00 for Elite Dragonfly G3, or 01.11.00 for Elite Dragonfly G2/Max and Elite X2 G8 Tablet)
Caveat BIOS updates carry a risk of system unavailability if interrupted; ensure stable power and do not power off during 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-2022-27538 — 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-27538 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