Bug 1745637 (CVE-2019-1552) - CVE-2019-1552 openssl: Insecure path defaults vulnerability in mingw builds
Summary: CVE-2019-1552 openssl: Insecure path defaults vulnerability in mingw builds
Alias: CVE-2019-1552
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1745640 1745650 1745651 1746041 1746042 1803847
Blocks: 1745641
TreeView+ depends on / blocked
Reported: 2019-08-26 14:33 UTC by Dhananjay Arunesh
Modified: 2023-09-07 20:28 UTC (History)
39 users (show)

Fixed In Version: OpenSSL 1.1.1d, OpenSSL 1.1.0l, OpenSSL 1.0.2t
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-10-27 10:55:07 UTC

Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-08-26 14:33:50 UTC
OpenSSL has internal defaults for a directory tree where it can find a configuration file as well as certificates used for verification in TLS. This directory is most commonly referred to as OPENSSLDIR, and is configurable with the --prefix / --openssldir configuration options. For OpenSSL versions 1.1.0 and 1.1.1, the mingw configuration targets assume that resulting programs and libraries are installed in a Unix-like environment and the default prefix for program installation as well as for OPENSSLDIR should be '/usr/local'. However, mingw programs are Windows programs, and as such, find themselves looking at sub-directories of 'C:/usr/local', which may be world writable, which enables untrusted users to modify OpenSSL's default configuration, insert CA certificates, modify (or even replace) existing engine modules, etc. For OpenSSL 1.0.2, '/usr/local/ssl' is used as default for OPENSSLDIR on all Unix and Windows targets, including Visual C builds. However, some build instructions for the diverse Windows targets on 1.0.2 encourage you to specify your own --prefix. OpenSSL versions 1.1.1, 1.1.0 and 1.0.2 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time.

Upstream commit:

Comment 1 Dhananjay Arunesh 2019-08-26 14:35:46 UTC
External References:


Comment 2 Dhananjay Arunesh 2019-08-26 15:00:54 UTC
Created openssl tracking bugs for this issue:

Affects: fedora-all [bug 1745650]

Comment 3 msiddiqu 2019-08-26 15:01:00 UTC
Created openssl tracking bugs for this issue:

Affects: fedora-all [bug 1745651]

Comment 4 Tomas Mraz 2019-08-26 15:47:05 UTC
This does NOT affect openssl. Only mingw-openssl.

Comment 5 Joshua Padman 2019-08-27 10:58:28 UTC
This vulnerability is out of security support scope for the following products:
 * Red Hat Enterprise Application Platform 5
 * Red Hat Enterprise Application Platform 6
 * Red Hat JBoss Core Services
 * Red Hat JBoss Enterprise Web Server 2
 * Red Hat JBoss Web Server 3 

Please refer to https://access.redhat.com/support/policy/updates/jboss_notes for more details.

However, all middleware products include openssl and this flaw only affects mingw-openssl.

Comment 6 Dhananjay Arunesh 2019-08-27 14:25:28 UTC
Created mingw-openssl tracking bugs for this issue:

Affects: epel-7 [bug 1746042]
Affects: fedora-all [bug 1746041]

Comment 9 Marco Benatto 2020-02-17 15:33:25 UTC

This issue only affects mingw-openssl builds, which are not shipped with any version of Red Hat Enterprise Linux.

Note You need to log in before you can comment on or make changes to this bug.