LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14318: Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation.

Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Crypto++ 8.3.0 and earlier may leak ECDSA private keys through timing differences during signing. An attacker who can observe many signing operations could recover the key. This is most urgent for services that repeatedly sign attacker-influenced data or expose signing behavior over a network. Exposure depends on whether an application embeds Crypto++ 8.3.0 or earlier and uses it for ECDSA signing. Network services, authentication systems, licensing systems, or APIs that perform repeated signatures for users are higher risk. Systems using Crypto++ without ECDSA signing are not directly exposed by this CVE. Prioritize systems where Crypto++ performs ECDSA signing for externally reachable services. The business impact is key compromise, which can undermine authentication, signing trust, or transaction integrity. Treat confirmed exposed signing services as high priority even though no active exploitation evidence is provided. Mitigation focus: Inventory applications and dependencies using Crypto++ 8.3.0 or earlier.; Check Crypto++ and OS vendor guidance for fixed packages or recommended updates.; Apply relevant distro or vendor security updates where available..

Prepared

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-2019-14318 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.