Bug 1732418 (CVE-2019-13509) - CVE-2019-13509 docker: Docker Engine in debug mode may sometimes add secrets to the debug log leading to information disclosure
Summary: CVE-2019-13509 docker: Docker Engine in debug mode may sometimes add secrets ...
Alias: CVE-2019-13509
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1732419 1732420 1748835
Blocks: 1732421
TreeView+ depends on / blocked
Reported: 2019-07-23 10:51 UTC by Marian Rehak
Modified: 2021-10-27 10:55 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-10-27 10:55:28 UTC

Attachments (Terms of Use)

Description Marian Rehak 2019-07-23 10:51:22 UTC
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.

Upstream Issue:


Comment 1 Marian Rehak 2019-07-23 10:51:43 UTC
Created docker tracking bugs for this issue:

Affects: epel-6 [bug 1732420]
Affects: fedora-all [bug 1732419]

Comment 4 Riccardo Schirone 2019-09-03 17:53:04 UTC
Upstream patch in the projectatomic/docker repository:

Comment 6 Riccardo Schirone 2019-09-04 08:56:24 UTC

This issue does affect the versions of docker as shipped with Red Hat Enterprise Linux 7, however debug mode on the daemon needs to be explicitly enabled as the docker systemd service, by default, does not enable debug mode.

Red Hat Fuse provides only the Docker client library and is not affected by this vulnerability.

Comment 7 Riccardo Schirone 2019-09-04 09:14:27 UTC
Function maskSecretKeys() in api/server/middleware/debug.go masks some sensitive data when logging them, by replacing the real content with a set of asterisk. However the "Data" field was not properly masked in all cases, thus allowing an attacker to possibly see those sensitive data in the docker daemon log.

Those logs should be anyway only visible by an administrator or an high-privileged user, but it may happen that a debug log is uploaded or shared when there is an issue and it is important to prevent secrets from leaking.

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