CVE-2016-6595
Last modified
CVE-2016-6595 is a vulnerability of currently unknown severity. 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. EPSS estimates a 2.45% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Docker | Docker | 1.12.0 |
References
- http://www.openwall.com/lists/oss-security/2016/08/04/1Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/09/02/1Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/09/02/8Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/08/04/1Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/09/02/1Third Party Advisory
- http://www.openwall.com/lists/oss-security/2016/09/02/8Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-6595?
How severe is CVE-2016-6595?
How do I fix CVE-2016-6595?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-6589A Denial of Service vulnerability exists in the ITMS workflo…6.5
- CVE-2016-6590A privilege escalation vulnerability exists when loading DLL…7.8
- CVE-2016-6591A security bypass vulnerability exists in Symantec Norton Ap…7.1
- CVE-2016-6592A vulnerability was found in Symantec Norton Download Manage…7.8
- CVE-2016-6593A code-execution vulnerability exists during startup in jhi.…7.8
- CVE-2016-6594Blue Coat Advanced Secure Gateway 6.6, CacheFlow 3.4, ProxyS…
- CVE-2016-6597Sophos EAS Proxy before 6.2.0 for Sophos Mobile Control, whe…
- CVE-2016-6598BMC Track-It! 11.4 before Hotfix 3 exposes an unauthenticate…
- CVE-2016-6599BMC Track-It! 11.4 before Hotfix 3 exposes an unauthenticate…
- CVE-2016-6600Directory traversal vulnerability in the file upload functio…
- CVE-2016-6601Directory traversal vulnerability in the file download funct…
- CVE-2016-6602ZOHO WebNMS Framework 5.2 and 5.2 SP1 use a weak obfuscation…
Are you affected by CVE-2016-6595?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
