Skip to content
Fencer Intel
high 7.5

CVE-2019-13509 json

Secret insertion into debug log in Docker

published 7y ago modified last mo. also GHSA-j249-ghv5-7mxv , EUVD-2022-4252

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/docker/docker 18.09.8
  • docker docker 18.09.8
  • docker.io Debian 14, Debian 13, Debian 12 18.09.1+dfsg1-8

debian advisories DEBIAN-CVE-2019-13509

  • docker-stable SLES for SAP 15 SP5, SLES for SAP 15 SP4, SLES for SAP 15 SP3 +12 more 24.0.9_ce-150000.1.25.1
  • golang-github-docker-libnetwork SLE Module for Containers 12, OpenStack Cloud 6-LTSS 0.7.0.1+gitr2800_fc5a7d91d54c-25.1
  • docker SLE Module for Containers 12, OpenStack Cloud 6-LTSS 19.03.1_ce-98.46.1
  • containerd SLE Module for Containers 12, OpenStack Cloud 6-LTSS 1.2.6-16.23.1
  • docker-runc SLE Module for Containers 12, OpenStack Cloud 6-LTSS 1.0.0rc8+gitr3826_425e105d5a03-1.29.1
  • golang-github-docker-libnetwork SLE Module for Containers 15 SP1, SLE Module for Containers 15 0.7.0.1+gitr2800_fc5a7d91d54c-4.15.1
  • docker SLE Module for Containers 15 SP1, SLE Module for Containers 15 19.03.1_ce-6.26.2
  • containerd SLE Module for Containers 15 SP1, SLE Module for Containers 15 1.2.6-5.16.1

suse advisories SUSE-SU-2025:03545-1SUSE-SU-2025:03540-1SUSE-SU-2019:2119-1SUSE-SU-2019:2117-1

  • docker-stable openSUSE Tumbleweed 24.0.9_ce-15.1
  • docker openSUSE Tumbleweed 20.10.6_ce-2.1
  • golang-github-docker-libnetwork openSUSE Leap 15.1, openSUSE Leap 15.0 0.7.0.1+gitr2800_fc5a7d91d54c-lp151.2.6.1
  • docker openSUSE Leap 15.1, openSUSE Leap 15.0 19.03.1_ce-lp151.2.12.1
  • containerd openSUSE Leap 15.1, openSUSE Leap 15.0 1.2.6-lp151.2.6.1
  • docker-runc openSUSE Leap 15.1, openSUSE Leap 15.0 1.0.0rc8+gitr3826_425e105d5a03-lp151.3.6.1

opensuse advisories openSUSE-SU-2025:15589-1openSUSE-SU-2024:10722-1openSUSE-SU-2019:2021-1

  • docker Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 18.09.8-r0
  • docker Alpine 3.11, Alpine 3.9 18.09.8

alpine advisories ALPINE-CVE-2019-13509

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-13509 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-13509 updated cvss 6.5

docker: Docker Engine in debug mode may sometimes add secrets to the debug log leading to information disclosure

  • Red Hat Enterprise Linux 7 docker
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7 docker
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.65% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/docker/docker
<18.09.8
18.09.8

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.