CVE-2024-4143
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 · uneditedA potential security vulnerability has been identified in certain HP PC products using AMI BIOS, which might allow arbitrary code execution. AMI has released firmware updates to mitigate this 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 · moderate confidenceA critical vulnerability in AMI BIOS firmware used in certain HP PC products allows arbitrary code execution. With a CVSS score of 9.8, this could enable an attacker to run malicious code at the firmware level, potentially bypassing operating system security controls and persisting across system reboots.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 model numberRun 'wmic csproduct get name' or check the physical system label/sticker for the model number (e.g., HP EliteBook, HP ProDesk, HP ZStation)Affected if The model is one of the HP PC products listed in the official HP security bulletin for CVE-2024-4143
-
Retrieve the current BIOS/firmware versionRun 'wmic bios get smbiosbiosversion' or check BIOS setup (F10 during boot) under the Main or Information section for the BIOS version stringAffected if The installed BIOS version is lower than the fixed version specified in HP's advisory for this CVE
-
Verify the system is using AMI BIOS firmwareRun 'wmic bios get manufacturer' or check the BIOS setup Information page for the BIOS vendor - look for American Megatrends Inc. (AMI)Affected if The BIOS manufacturer is American Megatrends (AMI) and the version is unpatched for this CVE
-
Check for available HP firmware updatesVisit HP's support website, enter your product number, and check the Security Bulletin section or BIOS update downloads for CVE-2024-4143Affected if HP has released a BIOS update for your model that addresses this CVE and your current version is older
-
Confirm the vulnerability is exploitable in your configurationThis is a firmware-level flaw in AMI BIOS - no specific configuration toggle is required; exploitation occurs through the vulnerable BIOS code itselfAffected if You are running an unpatched AMI BIOS version on an affected HP product model
You are affected if you have an HP system with an AMI BIOS version that is older than the fixed version HP has released for your specific model to address CVE-2024-4143.
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 the AMI firmware updates provided by HP for affected products. This typically involves downloading the latest BIOS/firmware version from HP's support website and following the vendor's firmware update procedure, ensuring uninterrupted power during the update process.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4143 — 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-2024-4143 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