# CVE-2023-28383: Privilege escalation in Intel(R) BIOS PPAM firmware

> A privileged local attacker can escalate privileges due to improper conditions checks in Intel BIOS PPAM firmware.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-6px8-gfpp-6wpc

## What is CVE-2023-28383?

CVE-2023-28383 is a medium-severity vulnerability in Intel(R) BIOS PPAM firmware, published on 16 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper conditions check in some Intel(R) BIOS PPAM firmware may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-92 (DEPRECATED: Improper Sanitization of Custom Special Characters)

## Which versions are affected by CVE-2023-28383?


## How do I fix CVE-2023-28383?

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

## Is CVE-2023-28383 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28383 and fix it if it is affected.

What it is: CVE-2023-28383 is a medium-severity vulnerability in Intel(R) BIOS PPAM firmware, published on 16 May 2024. 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-2023-28383 in the wild and no public exploit code.

Affected product: Intel(R) BIOS PPAM firmware. 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-2023-28383/ (Markdown: https://insights.sbomify.com/CVE-2023-28383/index.md)
```

## Sources

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

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