dbcve.org
Desktop Pro A 300 G3 FirmwareOperating system · Hp

CVE-2023-26300

HIGH · 7.8 CVSS v3.1 Published 2023-10-18
Fix available
A fix is available. Upgrade to 00.01.13 or later.
See remediation →
80/100
Remediation priority · High
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 security vulnerability has been identified in the system BIOS for certain HP PC products which might allow escalation of privilege. HP is releasing firmware 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
Desktop Pro A 300 G3 FirmwareOperating system
Affected:< f.13
Desktop Pro A G3 FirmwareOperating system
Affected:< f.13
Desktop Pro A G3 Microtower FirmwareOperating system
Affected:< f.13
Zhan 66 Pro A G1 R Microtower FirmwareOperating system
Affected:< f.13
T638 Thin Client FirmwareOperating system
Affected:< 00.01.13
Stream 11 Pro G5 FirmwareOperating system
Affected:< f.18
240 G10 FirmwareOperating system
Affected:< f.05
240 G6 FirmwareOperating system
Affected:< f.55

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

CVSS:3.1/AV:L/AC:L/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 00.01.13 or later
Fixed in 00.01.13
Vendor patch support.hp.com →
Recommended fix High confidence

BIOS firmware version f.13 or higher (Desktop Pro A 300 G3, Desktop Pro A G3, Desktop Pro A G3 Microtower, Zhan 66 Pro A G1 R Microtower); 00.01.13 or higher (T638 Thin Client); f.18 or higher (Stream 11 Pro G5); f.05 or higher (240 G10); f.55 or higher (240 G6)

  1. Visit HP's support website at https://support.hp.com/us-en/document/ish_9461800-9461828-16 to download the appropriate BIOS firmware update for your specific HP product model
  2. Identify your exact HP product model from the affected list: Desktop Pro A 300 G3, Desktop Pro A G3, Desktop Pro A G3 Microtower, Zhan 66 Pro A G1 R Microtower, T638 Thin Client, Stream 11 Pro G5, 240 G10, or 240 G6
  3. Download the BIOS update file corresponding to your product model
  4. Review HP's update instructions carefully before proceeding
  5. Run the BIOS update executable or use HP's BIOS update utility to install the new firmware version
  6. Ensure the system remains powered on and do not interrupt the update process until completion
  7. After the update completes, restart the system to ensure the new BIOS firmware is properly loaded
Caveat BIOS updates carry inherent risk of system incompatibility; ensure correct model-specific update is applied; HP recommends backing up data before performing BIOS updates

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-2023-26300 — 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-2023-26300 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