How severe is CVE-2013-1624?

No CVSS score has been assigned to CVE-2013-1624 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-1624?

CVE-2013-1624 affects the following packages: org.bouncycastle:bcprov-jdk15on (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-1624?

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

How do I detect CVE-2013-1624 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk15on, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-1624 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.

Is CVE-2013-1624 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-1624 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 CVE-2013-1624?

CVE-2013-1624 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th 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 CVE-2013-1624?

CVE-2013-1624 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 CVE-2013-1624 published, and has it been updated?

CVE-2013-1624 was published on February 8, 2013 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2013-1624: bcprov-jdk15on

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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`org.bouncycastle:bcprov-jdk15on:1.48`

Affected Products

2 products · 56 configurations

Application

bc-javabouncycastle

47 versions

1.011.021.031.041.051.061.071.081.091.101.111.12

Application

legion-of-the-bouncy-castle-c\#-cryptography-apibouncycastle

9 versions

0.01.01.11.21.31.41.51.6.11.7

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2013-1624 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss A-MQ 6.1	see advisory	RHSA-2014:0401
Red Hat JBoss BPMS 6.0	see advisory	RHSA-2014:0371
Red Hat JBoss BRMS 6.0	see advisory	RHSA-2014:0372
Red Hat JBoss Fuse 6.1	see advisory	RHSA-2014:0400
Red Hat JBoss Portal 6.2	`bouncycastle`	RHSA-2015:1009
Red Hat JBoss Web Framework Kit 2.6	see advisory	RHSA-2014:0896

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 CVE-2013-1624 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2013-1624 — bcprov-jdk15on