# CVE-2023-47282: Memory corruption in Intel(R) oneVPL software

> An authenticated local attacker can exploit an out-of-bounds write in Intel Media SDK to escalate privileges.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **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:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-47282, GHSA-jq7r-26j9-qj83, UBUNTU-CVE-2023-47282

## What is CVE-2023-47282?

CVE-2023-47282 is a low-severity memory corruption vulnerability in Intel(R) oneVPL software, 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

Out-of-bounds write in Intel(R) Media SDK all versions and some Intel(R) oneVPL software before version 23.3.5 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2023-47282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47282 is a low-severity memory corruption vulnerability in Intel(R) oneVPL software, 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-47282 in the wild and no public exploit code.

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

## Sources

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

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