# CVE-2022-22488: IBM OpenBMC denial of service

> A privileged user can cause a denial of service in IBM OpenBMC by rapidly uploading or deleting excessive CA certificates.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2022
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-25r2-v989-pqgp

## What is CVE-2022-22488?

CVE-2022-22488 is a medium-severity denial of service vulnerability in IBM OpenBMC, published on 18 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM OpenBMC OP910 and OP940 could allow a privileged user to cause a denial of service by uploading or deleting too many CA certificates in a short period of time.  IBM X-Force ID:  2226337.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2022-22488?

It affects 3 products.


Products: Ibm Power System Ac922 \(8335-Gtg\) Firmware, Ibm Power System Ac922 \(8335-Gth\) Firmware, Ibm Power System Ac922 \(8335-Gtx\) Firmware.

## How do I fix CVE-2022-22488?

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

## Is CVE-2022-22488 being exploited?

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

## Other vulnerabilities in IBM OpenBMC

- [CVE-2018-1992](https://insights.sbomify.com/CVE-2018-1992/): Memory corruption in Power 9 Systems (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22488 and fix it if it is affected.

What it is: CVE-2022-22488 is a medium-severity denial of service vulnerability in IBM OpenBMC, published on 18 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22488 in the wild and no public exploit code.

Affected product: IBM OpenBMC. 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-2022-22488/ (Markdown: https://insights.sbomify.com/CVE-2022-22488/index.md)
```

## Sources

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

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