Docker config secrets leaked when file is malformed and loglevel >= 4
In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects < v1.19.3, < v1.18.10, < v1.17.13.
- Published
- Dec 7, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 38th percentile
- CWE
- CWE-532
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 5.5
- CNA · kubernetes
- 4.7
- 0.8 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| kubernetes | kubernetes | cpe:2.3:a:kubernetes:kubernetes |
Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetes1.17.0 and later · before 1.17.13
- kubernetes kubernetes1.18.0 and later · before 1.18.10
- kubernetes kubernetes1.19.0 and later · before 1.19.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.
Kubernetes Kubernetes
- < 1.19.3, < 1.18.10, < 1.17.13affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | kubernetes | before 1.19.3-1 | 1.19.3-1 |
| Go | github.com/kubernetes/kubernetes | from 1.18.0 · before 1.18.10 | 1.18.10 |
| Go | github.com/kubernetes/kubernetes | from 1.19.0 · before 1.19.3 | 1.19.3 |
| Go | github.com/kubernetes/kubernetes | before 1.17.13 | 1.17.13 |
| Go | k8s.io/kubernetes | before 1.20.0-alpha.1 | 1.20.0-alpha.1 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-sdn-ovs | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-template-service-broker | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-tests | before 0:3.11.501-1.git.0.f8c4746.el7 | 0:3.11.501-1.git.0.f8c4746.el7 |
| Red Hat:openshift:4.6::el7 | openshift | before 0:4.6.0-202101160934.p0.git.94242.fc5242e.el7 | 0:4.6.0-202101160934.p0.git.94242.fc5242e.el7 |
| Red Hat:openshift:4.6::el7 | openshift-clients | before 0:4.6.0-202010081244.p0.git.3794.4743d24.el7 | 0:4.6.0-202010081244.p0.git.3794.4743d24.el7 |
| Red Hat:openshift:4.6::el7 | openshift-clients-redistributable | before 0:4.6.0-202010081244.p0.git.3794.4743d24.el7 | 0:4.6.0-202010081244.p0.git.3794.4743d24.el7 |
| Red Hat:openshift:4.6::el7 | openshift-hyperkube | before 0:4.6.0-202101160934.p0.git.94242.fc5242e.el7 | 0:4.6.0-202101160934.p0.git.94242.fc5242e.el7 |
| Red Hat:openshift:4.6::el7 | runc | before 0:1.0.0-81.rhaos4.6.git5b757d4.el7 | 0:1.0.0-81.rhaos4.6.git5b757d4.el7 |
| Red Hat:openshift:4.6::el7 | runc-debuginfo | before 0:1.0.0-81.rhaos4.6.git5b757d4.el7 | 0:1.0.0-81.rhaos4.6.git5b757d4.el7 |
+25
Same product
kubernetes: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the65This week
- CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port55Plan
- CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with 42Plan
- CVE-2018-1002101In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Wi40Plan
- CVE-2017-1000056Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to40Plan
- CVE-2016-1906Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that 40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:kubernetes | 1.19.3-1 · Debian:12 | Package registry (OSV) |
| Go:github.com/kubernetes/kubernetes | 1.17.13 | Package registry (OSV) |
| Go:github.com/kubernetes/kubernetes | 1.18.10 | Package registry (OSV) |
| Go:github.com/kubernetes/kubernetes | 1.19.3 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.20.0-alpha.1 | Package registry (OSV) |
| red hat:containers-common | 1:1.1.1-2.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.6.1601368321-1.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:openshift-clients | 0:4.6.0-202010081244.p0.git.3794.4743d24.el7 · Red Hat:openshift:4.6::el7 | Package registry (OSV) |
| red hat:openshift-clients-redistributable | 0:4.6.0-202010081244.p0.git.3794.4743d24.el7 · Red Hat:openshift:4.6::el7 | Package registry (OSV) |
| red hat:podman | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:podman-debuginfo | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:podman-debugsource | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:podman-docker | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:podman-remote | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:podman-remote-debuginfo | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:podman-tests | 0:1.9.3-3.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:skopeo | 1:1.1.1-2.rhaos4.6.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/kubernetes/kubernetes/issues/95622
- groups.google.com/g/kubernetes-security-discuss/c/vm-HcrFUOCs/m/36utxAM5CwAJ
- security.netapp.com/advisory/ntap-20210122-0006/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.