CVE-2016-6595
What it is
The SwarmKit toolkit 1.12.0 for Docker allows remote authenticated users to cause a denial of service (prevention of cluster joins) via a long sequence of join and quit actions. NOTE: the vendor disputes this issue, stating that this sequence is not "removing the state that is left by old nodes. At some point the manager obviously stops being able to accept new nodes, since it runs out of memory. Given that both for Docker swarm and for Docker Swarmkit nodes are *required* to provide a secret token (it's actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can't do anything about a manager running out of memory and not being able to add new legitimate nodes to the system. This is merely a resource provisioning issue, and definitely not a CVE worthy vulnerability.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of service disruption.
- Exploit odds
- 2.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.8% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 2.8% · EPSS, next 30 days
- Weakness
- CWE-399
- Record status
- Modified
Affected
- Docker 1.12.0
Attack profile CVSS 3.0 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-6595.md and follow it. Check whether this project is affected by CVE-2016-6595. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://www.openwall.com/lists/oss-security/2016/08/04/1
- http://www.openwall.com/lists/oss-security/2016/09/02/1
- http://www.openwall.com/lists/oss-security/2016/09/02/8
- http://www.securityfocus.com/bid/92195
- http://www.securitytracker.com/id/1036548
- http://www.openwall.com/lists/oss-security/2016/08/04/1
- http://www.openwall.com/lists/oss-security/2016/09/02/1
- http://www.openwall.com/lists/oss-security/2016/09/02/8
- http://www.securityfocus.com/bid/92195
- http://www.securitytracker.com/id/1036548