CVE-2019-1551

Public on

Last Modified: UTC

Low Low Impact What does this mean?
4.8 CVSS v3 Base Score

Description

An integer overflow was found in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. As per upstream:

  • No EC algorithms are affected.

  • 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

Statement

Accelerated modular exponentiation for Intel processors (RSAZ) was introduced in openssl-1.0.2, therefore older versions of OpenSSL are not affected by this flaw.

Mitigation

For Red Hat Enterprise Linux 7, 512 bit DH is already disabled. As this bug is about leakage of the private key to the attacker, it should be fully sufficient to just not use 1024 bit RSA keys or 1024 bit DSA keys. These keys are not secure enough anyway. 3-prime RSA keys are not supported on RHEL-7.

For Red Hat Enterprise 8, The DEFAULT crypto policy already disables all these key sizes.

Also applications compiled with openssl which use the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME, other users of this API are not affected by this flaw.

Additional Information

External References

Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2019-1551

Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2019-1551

Content from github.com is not included.https://github.com/openssl/openssl/pull/10575

Content from www.openssl.org is not included.https://www.openssl.org/news/secadv/20191206.txt

Affected Packages and Issued Red Hat Security Errata

Products / Services Components State Errata
JBoss Core Services on RHEL 6 jbcs-httpd24-apr Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-apr-util Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-brotli Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-curl Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-httpd Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-jansson Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-mod_cluster-native Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-mod_http2 Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-mod_jk Fixed RHSA-2020:4384
JBoss Core Services on RHEL 6 jbcs-httpd24-mod_md Fixed RHSA-2020:4384
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown Red Hat NVD
CVSS v3 Base Score 4.8 5.3
Attack Vector Network Network
Attack Complexity High Low
Privileges Required None None
User Interaction None None
Scope Unchanged Unchanged
Confidentiality Impact Low Low
Integrity Impact Low None
Availability Impact None None

CVSS v3 Vector

Red Hat CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Red Hat CVSS v3 Score Explanation

This attack works with 512-bit moduli DH, however, for an attack the target would have to re-use the DH512 private key, which is not a recommended crypto practice. Therefore this flaw has been classified as having high attack complexity. (AC:H)

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.

My product is listed as "Out of Support Scope". What does this mean?

 When a product is listed as "Out of Support Scope", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase. The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed. The product should be assumed to be affected. Customers are advised to apply any mitigation options documented on this page, consider removing or disabling the impacted component, or upgrade to a supported version of the product that has an update available.