Host API access via guest-container exposure
Published Jan 17, 2020 · Updated Sep 17, 2024
Resource exposure in docker-kubic on SUSE CaaS Platform 3.0 allows local users in master-node containers to access an insecure API. The public record identifies neither the API or port nor the configuration error that makes it reachable from guest containers on the Kubernetes master node. Access requires execution inside a guest container on that master node; the callable operations and resulting data or service effects remain undisclosed.
Summary
What happened
Resource exposure in docker-kubic on SUSE CaaS Platform 3.0 allows local users in master-node containers to access an insecure API. The public record identifies neither the API or port nor the configuration error that makes it reachable from guest containers on the Kubernetes master node. Access requires execution inside a guest container on that master node; the callable operations and resulting data or service effects remain undisclosed.
The record
- CVE
- CVE-2019-3682
- Published
- Jan 17, 2020
- Updated
- Sep 17, 2024
- Vendor
- SUSE
- Product
- SUSE CaaS Platform
- Classifications
- CWE-668
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 17, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=docker-kubic <17.09.1_ce-7.6.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo