# CVE-2024-5477: Privilege escalation in Certain HP PC Products

> Physical attackers with specialized equipment can exploit HP PC BIOS to escalate privileges, execute code, cause denial of service, or disclose information.

- **Severity:** High 7.3 (`CVSS:4.0/AV:P/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-mmhv-hfp7-cg3c

## What is CVE-2024-5477?

CVE-2024-5477 is a high-severity vulnerability in Certain HP PC Products, published on 13 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential security vulnerability has been identified in the System BIOS for some HP PC products which may allow escalation of privilege, arbitrary code execution, denial of service, or information disclosure via a physical attack that requires specialized equipment and knowledge.  HP is releasing firmware mitigation for the potential vulnerability.

Weakness: CWE-1256 (Improper Restriction of Software Interfaces to Hardware Features)

## Which versions are affected by CVE-2024-5477?


## How do I fix CVE-2024-5477?

No fix has been published for CVE-2024-5477 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5477 being exploited?

There is no known exploitation of CVE-2024-5477 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5477 and fix it if it is affected.

What it is: CVE-2024-5477 is a high-severity vulnerability in Certain HP PC Products, published on 13 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5477 in the wild and no public exploit code.

Affected product: Certain HP PC Products. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5477/ (Markdown: https://insights.sbomify.com/CVE-2024-5477/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5477
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5477
- OSV: https://osv.dev/vulnerability/CVE-2024-5477

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5477/
Summaries are generated and may contain mistakes; the official description above is the record.