# CVE-2022-45146: Garbage collection issue in BC-FJA in Java 13 and later

> A use-after-free vulnerability in Bouncy Castle FIPS Java API allows temporary keys to be zeroed while in use, potentially causing errors or information loss.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-68m8-v89j-7j2p

## What is CVE-2022-45146?

CVE-2022-45146 is a medium-severity use after free vulnerability in n/a, published on 21 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the FIPS Java API of Bouncy Castle BC-FJA before 1.0.2.4. Changes to the JVM garbage collector in Java 13 and later trigger an issue in the BC-FJA FIPS modules where it is possible for temporary keys used by the module to be zeroed out while still in use by the module, resulting in errors or potential information loss. NOTE: FIPS compliant users are unaffected because the FIPS certification is only for Java 7, 8, and 11.

Weakness: CWE-416 (Use After Free)

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

2 open source packages ship an affected version, including org.bouncycastle:bc-fips. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.bouncycastle:bc-fips` | Maven | All versions | 1.0.2.4 |
| `org.bouncycastle:bc-fips` | Maven | All versions | 1.0.2.4 |

Products: Bouncycastle Fips Java Api.

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

Upgrade org.bouncycastle:bc-fips to 1.0.2.4 or later.

## Is CVE-2022-45146 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26939](https://insights.sbomify.com/CVE-2020-26939/): Observable Differences in Behavior to Error Inputs in Bouncy Castle (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45146 is a medium-severity use after free vulnerability in n/a, published on 21 Nov 2022. 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-2022-45146 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.bouncycastle:bc-fips (Maven): affected all versions; fixed in 1.0.2.4
- org.bouncycastle:bc-fips (Maven): affected all versions; fixed in 1.0.2.4

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-45146/ (Markdown: https://insights.sbomify.com/CVE-2022-45146/index.md)
```

## Sources

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

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