---
id: CVE-2019-1552
title: Windows builds with insecure path defaults
summary: >-
  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 --pre…
severity: none
vendor: OpenSSL
product: OpenSSL
affected:
  - OpenSSL Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c)
  - OpenSSL Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k)
  - OpenSSL Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s)
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-02T17:46:33.312082Z'
published: '2019-07-30'
updated: '2026-11-02'
sourceUpdated: '2026-11-02T17:46:44.615Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2019-1552'
references:
  - url: >-
      https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EWC42UXL5GHTU5G77VKBF6JYUUNGSHOM/
    label: FEDORA-2019-db06efdea1
  - url: >-
      https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/
    label: FEDORA-2019-00c25b9379
  - url: >-
      https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/
    label: FEDORA-2019-9a0a7c0986
  - url: 'https://www.oracle.com/security-alerts/cpuapr2020.html'
  - url: 'https://www.oracle.com/security-alerts/cpujul2020.html'
  - url: >-
      https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
  - url: 'https://www.tenable.com/security/tns-2019-08'
  - url: 'https://www.oracle.com/security-alerts/cpujan2020.html'
  - url: 'https://www.tenable.com/security/tns-2019-09'
  - url: 'https://www.openssl.org/news/secadv/20190730.txt'
  - url: >-
      https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=54aa9d51b09d67e90db443f682cface795f5af9e
  - url: >-
      https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=e32bc855a81a2d48d215c506bdeb4f598045f7e9
  - url: >-
      https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=b15a19c148384e73338aa7c5b12652138e35ed28
  - url: >-
      https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=d333ebaf9c77332754a9d5e111e2f53e1de54fdd
  - url: 'https://security.netapp.com/advisory/ntap-20190823-0006/'
  - url: 'https://support.f5.com/csp/article/K94041354'
  - url: >-
      https://support.f5.com/csp/article/K94041354?utm_source=f5support&amp%3Butm_medium=RSS
  - url: 'https://www.oracle.com/security-alerts/cpuoct2020.html'
  - url: 'https://www.kb.cert.org/vuls/id/429301'
    label: VU#429301
  - url: 'https://kc.mcafee.com/corporate/index?page=content&id=SB10365'
  - url: 'https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf'
tags:
  - cve.org
epss: 0.00695
epssPercentile: 0.53254
ingestedAt: '2026-11-05T19:30:42.748Z'
---

## Overview

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. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

## Affected

- `OpenSSL Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c)`
- `OpenSSL Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k)`
- `OpenSSL Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s)`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.