LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15522: Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA befo...

Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a cryptographic side-channel issue in older Bouncy Castle libraries. Under specific conditions, repeated timing observations during deterministic ECDSA signing could reveal private-key information. The business risk is highest where affected libraries sign valuable transactions, certificates, tokens, or software artifacts.

Executive priority

Treat this as a targeted cryptographic exposure review, not a broad emergency. Prioritize systems that sign high-value assets or transactions with affected Bouncy Castle versions, then follow vendor upgrade guidance and assess key-rotation need based on exposure evidence.

Technical view

CVE-2020-15522 affects Bouncy Castle BC Java before 1.66, BC C#/.NET before 1.8.7, BC-FJA before listed fixed builds, and BC-FNA before 1.0.1.1. The issue is in EC math timing behavior during multiple deterministic ECDSA signatures, potentially leaking private-key information to an observer.

Likely exposure

Exposure is likely in applications, appliances, or services that embed affected Bouncy Castle versions and perform deterministic ECDSA signing where an attacker can observe repeated timing behavior. The supplied data does not identify specific deployed products beyond the Bouncy Castle families and a NetApp advisory reference.

Exploitation context

No CISA KEV listing is provided, and the source bundle does not cite active exploitation. Practical risk depends on attacker ability to collect timing information across multiple signatures and on whether affected libraries are used for sensitive signing operations.

Researcher notes

The key uncertainty is operational exploitability. The vulnerability requires timing observation across multiple deterministic ECDSA signatures. Sources identify affected library versions and fixed version thresholds, but the bundle provides no CVSS, CWE, public exploit claim, or active-exploitation evidence.

Mitigation direction

  • Upgrade BC Java to 1.66 or later where applicable.
  • Upgrade BC C#/.NET to 1.8.7 or later where applicable.
  • Upgrade BC-FJA and BC-FNA to fixed versions named by vendor guidance.
  • Check appliance and software vendor advisories for embedded Bouncy Castle dependencies.
  • Rotate exposed signing keys if credible timing observation occurred.

Validation and detection

  • Inventory direct and transitive Bouncy Castle dependencies across applications and appliances.
  • Confirm deployed versions against the affected-version ranges in the CVE description.
  • Identify services performing deterministic ECDSA signing with affected libraries.
  • Review vendor advisories, including NetApp, for product-specific exposure and fixes.
  • Document whether sensitive private keys were used before remediation.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-15522 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.