CVE Intelligence
Medium Memory corruption

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).

Published Dec 6, 2019 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: openssl

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 14.3% (30-day exploitation probability)+14
  • Technical severity (medium)+3
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
14.3%
ahead of 97% of scored CVEs · Oct 15, 2026
Affects
Canonical
Ubuntu Linux and 8 more
CVSS base
5.3
Medium · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Canonical Ubuntu Linux version 16.04version 18.04version 19.10 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 9.0version 10.0 Vulnerable NIST National Vulnerability Database
Fedoraproject Fedora version 31version 32version 30 Vulnerable NIST National Vulnerability Database
Openssl Openssl version Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t)version Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d) Vulnerable CVE Program (cve.org) e CISA ADP
Openssl Openssl ≥ 1.1.1 and ≤ 1.1.1d≥ 1.0.2 and ≤ 1.0.2t Vulnerable NIST National Vulnerability Database
Opensuse Leap version 15.1 Vulnerable NIST National Vulnerability Database
Oracle Enterprise Manager Ops Center version 12.4.0.0 Vulnerable NIST National Vulnerability Database
Oracle Mysql Enterprise Monitor ≤ 4.0.12≥ 8.0.0 and ≤ 8.0.20 Vulnerable NIST National Vulnerability Database
Oracle Peoplesoft Enterprise Peopletools version 8.58version 8.57version 8.56 Vulnerable NIST National Vulnerability Database
Tenable Log Correlation Engine < 6.0.9 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 3.1 Medium 3.9 1.4 nvd@nist.gov via NIST National Vulnerability Database
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-190 · Integer Overflow or Wraparound

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 14.30%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · openssl/openssl
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2019
  • CVE published
    Dec 6, 2019 · openssl

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

24 on the record

Elsewhere on this site

Canonical
every CVE for this vendor
CWE-190
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-84784 QUIC: Unbounded RETIRE_CONNECTION_ID Backlog 16d
  • High CVE-2026-84783 Use-After-Free in X.509 Extension Cache Under Concurrent Use 16d
  • High CVE-2026-84782 DTLS Retransmits Handshake Messages From a Stale Buffer Offset 16d
  • Medium CVE-2026-75806 Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS 16d
  • Medium CVE-2026-75805 NULL Pointer Dereference in CMP Client Revocation Response Handling 16d
  • Low CVE-2026-77696 Timing Side-Channel in SM2 Signature Generation 16d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-1551 is "rsaz_512_sqr overflow bug on x86_64", rated Medium. It affects Ubuntu Linux (Canonical); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 14.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.