Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2020-28052

HIGH

CVE-2020-28052 is a high-severity (CVSS 8.1) vulnerability in org.bouncycastle:bcprov-jdk15to18. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-28052 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Logic error in Legion of the Bouncy Castle BC Java

Also known asGHSA-73xv-w5gp-frxh
Published
Dec 18, 2020
Updated
Aug 7, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
1 known

Real-World Exposure

7 pkgs affected
org.bouncycastle:bcprov-jdk15to18org.bouncycastle:bcprov-jdk15org.bouncycastle:bcprov-jdk15onorg.bouncycastle:bcprov-ext-jdk15onorg.bouncycastle:bcprov-jdk14org.bouncycastle:bcprov-jdk16org.bouncycastle:bcprov-ext-jdk16

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.bouncycastle:bcprov-jdk15to181.65&&< 1.671.67
Mavenorg.bouncycastle:bcprov-jdk151.65&&< 1.671.67
Mavenorg.bouncycastle:bcprov-jdk15on1.65&&< 1.671.67
Mavenorg.bouncycastle:bcprov-ext-jdk15on1.65&&< 1.671.67
Mavenorg.bouncycastle:bcprov-jdk141.65&&< 1.671.67
Mavenorg.bouncycastle:bcprov-jdk161.65&&< 1.671.67
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk15to18. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.bouncycastle:bcprov-jdk15to18 to 1.67 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28052 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-28052 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-28052. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different.
O3 Security · Impact-Aware SCA

Is CVE-2020-28052 in your dependencies?

O3 detects CVE-2020-28052 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.