# CVE-2023-34351: Memory corruption in Intel(R) PCM software

> An unauthenticated attacker can cause a denial of service in Intel PCM software via network access due to a buffer underflow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2024
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-85gr-f847-q6cw

## What is CVE-2023-34351?

CVE-2023-34351 is a high-severity memory corruption vulnerability in Intel(R) PCM software, published on 14 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer underflow in some Intel(R) PCM software before version 202307 may allow an unauthenticated user to potentially enable denial of service via network access.

Weakness: CWE-787 (Out-of-bounds Write), CWE-124 (Buffer Underwrite)

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

It affects 1 product.


Products: Intel Performance Counter Monitor.

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

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

## Is CVE-2023-34351 being exploited?

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

## Other vulnerabilities in Intel(R) PCM software

- [CVE-2026-32791](https://insights.sbomify.com/CVE-2026-32791/): Privilege escalation in Intel(R) Performance Counter Monitor (Intel(R) PCM) (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34351 is a high-severity memory corruption vulnerability in Intel(R) PCM software, published on 14 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-34351 in the wild and no public exploit code.

Affected product: Intel(R) PCM software. 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-34351/ (Markdown: https://insights.sbomify.com/CVE-2023-34351/index.md)
```

## Sources

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

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