How severe is GHSA-8353-fgcr-xfhx?

No CVSS score has been assigned to GHSA-8353-fgcr-xfhx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8353-fgcr-xfhx?

GHSA-8353-fgcr-xfhx affects the following packages: org.bouncycastle:bcprov-jdk15on (Maven). Ecosystems affected: Maven.

How do I fix GHSA-8353-fgcr-xfhx?

Update org.bouncycastle:bcprov-jdk15on to 1.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8353-fgcr-xfhx is resolved across your whole dependency graph.

How do I detect GHSA-8353-fgcr-xfhx in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk15on. 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.

How do I mitigate GHSA-8353-fgcr-xfhx if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-8353-fgcr-xfhx?

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

Is GHSA-8353-fgcr-xfhx actively exploited in the wild?

No public exploit code has been indexed for GHSA-8353-fgcr-xfhx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8353-fgcr-xfhx?

GHSA-8353-fgcr-xfhx has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8353-fgcr-xfhx?

GHSA-8353-fgcr-xfhx is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8353-fgcr-xfhx published, and has it been updated?

GHSA-8353-fgcr-xfhx was published on May 14, 2022 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-8353-fgcr-xfhx: Improper Input Validation in Bouncy Castle

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk85th percentile+2.58%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.bouncycastle:bcprov-jdk15on

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

The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.bouncycastle:bcprov-jdk15on`	all versions	1.48

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk15on. 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.
Fix
Update org.bouncycastle:bcprov-jdk15on to 1.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8353-fgcr-xfhx is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-8353-fgcr-xfhx 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 GHSA-8353-fgcr-xfhx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169.

O3 Security · Impact-Aware SCA

Is GHSA-8353-fgcr-xfhx in your dependencies?

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

Scan my dependencies How O3 SCA works

GHSA-8353-fgcr-xfhx