Skip to content
Fencer Intel
medium 5.5

CVE-2022-45146 json

Garbage collection issue in BC-FJA in Java 13 and later

published 3y ago modified last mo. also GHSA-68m8-v89j-7j2p , EUVD-2022-7255

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.bouncycastle:bc-fips 1.0.2.4
  • bouncycastle fips_java_api 1.0.2.4

Is CVE-2022-45146 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-45146 updated cvss 5.5

bouncy-castle: Improper Authentication

  • Red Hat Build of Keycloak bc-fips bc-fips Red Hat build of Quarkus org.bouncycastle/bc-fips org.bouncycastle/bc-fips Red Hat JBoss Enterprise Application Platform 8 bc-fips bc-fips Red Hat streams for Apache Kafka bc-fips bc-fips
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/bcgit/bc-java/wiki/CVE-2022-45146 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.bouncycastle:bc-fips
<1.0.2.4
1.0.2.4

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.