CVE intelligence and bounded remediation

CVE-2019-1551 — There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli

Medium CVSS 5.3

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

Severity
Medium
CVSS
5.3 (3.1)
Published
2019-12-06
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-190

Affected products

  • openssl / openssl
  • opensuse / leap / 15.1
  • oracle / enterprise_manager_ops_center / 12.4.0.0
  • oracle / mysql_enterprise_monitor
  • oracle / peoplesoft_enterprise_peopletools / 8.56
  • oracle / peoplesoft_enterprise_peopletools / 8.57

Showing 6 representative product identities from 18 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.