The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channe
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.
- Published
- Feb 8, 2013
- Updated
- Jun 16, 2026
- EPSS
- 3.0% · 87th percentile
- CWE
- CWE-310
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.0%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| bouncycastle | bc-java | cpe:2.3:a:bouncycastle:bc-java |
| bouncycastle | legion-of-the-bouncy-castle-c\#-cryptography-api | cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-c\#-cryptography-api |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- bouncycastle bc-java1.01
- bouncycastle bc-java1.02
- bouncycastle bc-java1.03
- bouncycastle bc-java1.04
- bouncycastle bc-java1.05
- bouncycastle bc-java1.06
- bouncycastle bc-java1.07
- bouncycastle bc-java1.08
- bouncycastle bc-java1.09
- bouncycastle bc-java1.10
- bouncycastle bc-java1.11
- bouncycastle bc-java1.12
- bouncycastle bc-java1.13
- bouncycastle bc-java1.14
- bouncycastle bc-java1.15
- bouncycastle bc-java1.16
- bouncycastle bc-java1.17
- bouncycastle bc-java1.18
- bouncycastle bc-java1.19
- bouncycastle bc-java1.20
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | bouncycastle | before 1.48+dfsg-2 | 1.48+dfsg-2 |
| Maven | org.bouncycastle:bcprov-jdk15on | before 1.48 | 1.48 |
Same product
bouncycastle: all recordsOther highest-scoring records for the same primary product.
- CVE-2007-6721The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impac41Plan
- CVE-2018-1000613Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of 40Plan
- CVE-2026-58062Stapled OCSP response accepted without binding to the checked certificate37Monitor
- CVE-2026-8763Name Constraints bypass via trailing dot in rfc822Name and URI37Monitor
- CVE-2026-59650MTI/A0 DH agreement exponentiates unvalidated peer value37Monitor
- CVE-2026-59638JSSE hostname verifier CN-fallback enabled by default despite documented opt-in37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:bouncycastle | 1.48+dfsg-2 · Debian:12 | Package registry (OSV) |
| Maven:org.bouncycastle:bcprov-jdk15on | 1.48 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- High
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:H/Au:N/C:P/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- openwall.com/lists/oss-security/2013/02/05/24
- rhn.redhat.com/errata/RHSA-2014-0371.html
- rhn.redhat.com/errata/RHSA-2014-0372.html
- secunia.com/advisories/57716
- secunia.com/advisories/57719
- www.isg.rhul.ac.uk/tls/TLStiming.pdf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.