Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2019-13509


In Docker CE and EE before 18.09.8 (as well as Docker EE before 17.06.2-ee-23 and 18.x before 18.03.1-ee-10), Docker Engine in debug mode may sometimes add secrets to the debug log. This applies to a scenario where docker stack deploy is run to redeploy a stack that includes (non external) secrets. It potentially applies to other API users of the stack API if they resend the secret.


Security Impact Summary

This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), for affected systems. Impacting 1 product from docker organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2019, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.


Published

2019-07-18T16:15:11.953

Last Modified

2024-11-21T04:25:02.213

Status

Modified

Source

[email protected]

Severity

CVSSv3.0: 7.5 (HIGH)

CVSSv2 Vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

  • Access Vector: NETWORK
  • Access Complexity: LOW
  • Authentication: NONE
  • Confidentiality Impact: PARTIAL
  • Integrity Impact: NONE
  • Availability Impact: NONE
Exploitability Score

10.0

Impact Score

2.9

Weaknesses
  • Type: Primary
    CWE-532

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application docker docker < 18.09.8 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.03.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 17.06.2 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker 18.03.1 Yes
Application docker docker < 18.09.8 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For docker's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.