# CVE-2023-32280: Hardcoded credentials in Intel(R) Server Product OpenBMC firmware

> Unauthenticated attackers can access sensitive information due to insufficiently protected credentials in Intel Server OpenBMC firmware.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 14 Aug 2024
- **Also known as:** GHSA-fmp2-6gj7-cwpc

## What is CVE-2023-32280?

CVE-2023-32280 is a medium-severity vulnerability in Intel(R) Server Product OpenBMC firmware, published on 14 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficiently protected credentials in some Intel(R) Server Product OpenBMC firmware before versions egs-1.05 may allow an unauthenticated user to enable information disclosure via network access.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Intel Openbmc.

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

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

## Is CVE-2023-32280 being exploited?

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

## Other vulnerabilities in Intel(R) Server Product OpenBMC firmware

- [CVE-2022-29494](https://insights.sbomify.com/CVE-2022-29494/): Denial of service in OpenBMC (medium 6.5)
- [CVE-2023-31189](https://insights.sbomify.com/CVE-2023-31189/): Privilege escalation in Intel(R) Server Product OpenBMC firmware (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32280 is a medium-severity vulnerability in Intel(R) Server Product OpenBMC firmware, 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-32280 in the wild and no public exploit code.

Affected product: Intel(R) Server Product OpenBMC firmware. 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-32280/ (Markdown: https://insights.sbomify.com/CVE-2023-32280/index.md)
```

## Sources

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

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