# CVE-2019-13509: Secret insertion into debug log in Docker

> Docker Engine in debug mode may leak secrets into logs during stack redeployment, exposing sensitive data to attackers with log access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** CLEANSTART-2026-MP51710, DEBIAN-CVE-2019-13509, GHSA-j249-ghv5-7mxv

## What is CVE-2019-13509?

CVE-2019-13509 is a high-severity vulnerability in n/a, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-13509?

2 open source packages ship an affected version, including github.com/docker/docker. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/docker/docker` | Go | All versions | 18.09.8 |
| `github.com/docker/docker` | Go | All versions | 18.09.8 |

Products: Docker Docker.

## How do I fix CVE-2019-13509?

Upgrade github.com/docker/docker to 18.09.8 or later.

## Is CVE-2019-13509 being exploited?

There is no known exploitation of CVE-2019-13509 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-9357](https://insights.sbomify.com/CVE-2014-9357/): Arbitrary Code Execution (critical 10.0)
- [CVE-2020-14298](https://insights.sbomify.com/CVE-2020-14298/): Privilege escalation in Docker (high 8.8)
- [CVE-2020-14300](https://insights.sbomify.com/CVE-2020-14300/): Privilege escalation in Docker (high 8.8)
- [CVE-2018-15514](https://insights.sbomify.com/CVE-2018-15514/): Deserialization in n/a (high 8.8)
- [CVE-2014-9356](https://insights.sbomify.com/CVE-2014-9356/): Path Traversal in Docker (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13509 and fix it if it is affected.

What it is: CVE-2019-13509 is a high-severity vulnerability in n/a, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13509 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/docker/docker (Go): affected all versions; fixed in 18.09.8
- github.com/docker/docker (Go): affected all versions; fixed in 18.09.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13509/ (Markdown: https://insights.sbomify.com/CVE-2019-13509/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13509
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13509
- OSV: https://osv.dev/vulnerability/CVE-2019-13509

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13509/
Summaries are generated and may contain mistakes; the official description above is the record.