# CVE-2023-39929: Privilege escalation in Libva software maintained by Intel(R)

> An authenticated local attacker can escalate privileges via an uncontrolled search path in Intel Libva software.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 May 2024
- **Updated:** 6 Sep 2024
- **Also known as:** AZL-48840, GHSA-4jmf-2ggr-ph9x, OESA-2024-1689, SUSE-SU-2025:1451-1, SUSE-SU-2025:1452-1, SUSE-SU-2025:1453-1, SUSE-SU-2025:1477-1, UBUNTU-CVE-2023-39929

## What is CVE-2023-39929?

CVE-2023-39929 is a medium-severity vulnerability in Libva software maintained by Intel(R), published on 16 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Uncontrolled search path in some Libva software maintained by Intel(R) before version 2.20.0 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libva` | SUSE:Enterprise Storage 7.1 | All versions | 2.20.0-150300.3.3.1 |
| `libva` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.20.0-150300.3.3.1 |
| `libva` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.20.0-150400.3.5.1 |
| `libva` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.20.0-150400.3.5.1 |
| `libva` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 2.20.0-150500.3.5.1 |
| `libva` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 2.20.0-150500.3.5.1 |
| `libva` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 2.20.0-3.3.4 |
| `libva` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 2.20.0-150300.3.3.1 |
| `libva` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.20.0-150400.3.5.1 |
| `libva` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 2.20.0-150500.3.5.1 |
| `libva` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.20.0-3.3.4 |
| `libva` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 2.20.0-150300.3.3.1 |
| `libva` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 2.20.0-150400.3.5.1 |
| `libva` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 2.20.0-150500.3.5.1 |

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

Upgrade to a fixed version.

## Is CVE-2023-39929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39929 is a medium-severity vulnerability in Libva software maintained by Intel(R), published on 16 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-39929 in the wild and no public exploit code.

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

## Sources

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

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