# CVE-2023-49614: Memory corruption in Intel(R) FPGA products

> Out-of-bounds write in Intel FPGA firmware allows attackers to escalate privileges and disclose sensitive information.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/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:** 15 Aug 2024
- **Also known as:** GHSA-j5g3-pfmw-cxm8

## What is CVE-2023-49614?

CVE-2023-49614 is a medium-severity memory corruption vulnerability in Intel(R) FPGA products, 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

Out of bounds write in firmware for some Intel(R) FPGA products before version 2.9.0 may allow escalation of privilege and information disclosure.

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

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


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

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

## Is CVE-2023-49614 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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