# CVE-2023-31276: Memory corruption in Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP

> A heap-based buffer overflow in Intel server board firmware allows privileged local users to escalate privileges.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 12 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-62xq-66fv-wc89

## What is CVE-2023-31276?

CVE-2023-31276 is a high-severity memory corruption vulnerability in Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap-based buffer overflow in BMC Firmware for the Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, before version 02.01.0017 and Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP before version R01.01.0009 may allow a privileged user to enable escalation of privilege via local access.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

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

## Is CVE-2023-31276 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31276 is a high-severity memory corruption vulnerability in Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP, published on 12 Feb 2025. 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-31276 in the wild and no public exploit code.

Affected product: Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP. 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-31276/ (Markdown: https://insights.sbomify.com/CVE-2023-31276/index.md)
```

## Sources

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

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