LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1551: rsaz_512_sqr overflow bug on x86_64

There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).

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

Security readout for executives and security teams

CVE-2019-1551 is an OpenSSL math bug affecting some 64-bit code paths. Most real-world attacks are described as very difficult, but DH512 with a reused private key is considered just feasible. Patch affected OpenSSL versions and remove weak 512-bit Diffie-Hellman use. Exposure is most likely on systems running affected OpenSSL versions, especially where DH512 is enabled or applications directly call BN_mod_exp with BN_FLG_CONSTTIME. Standard EC usage is not in scope based on the source bundle. Prioritize normal patch cycles, with faster action for internet-facing or legacy systems using weak DH512. The practical attack window appears narrow, but OpenSSL exposure can be widespread and should not remain untracked. Mitigation focus: Upgrade OpenSSL to 1.1.1e, 1.0.2u, or a vendor-fixed package.; Disable DH512 and replace it with stronger, supported Diffie-Hellman parameters.; Avoid reuse of DH512 private keys where legacy configurations still exist..

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-1551 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
23Source 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
OpenSSLOpenSSLFixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d), Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t)Listed
Weakness

CWE details

No CWE listed

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