Vulnerability-Lookup

CVE-2016-6595 (GCVE-0-2016-6595)

Vulnerability from cvelistv5 – Published: 2017-01-04 20:00 – Updated: 2024-08-06 01:36 Disputed

Summary

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.

Severity

6.5 (Medium)


                        
                          CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CWE

Assigner

mitre CNA under the mitre root

CNA scorecard E 28/100 over 2263 records in the last 180 days details

References

5 references

URL	Tags
http://www.openwall.com/lists/oss-security/2016/09/02/8	mailing-listx_refsource_MLIST
http://www.openwall.com/lists/oss-security/2016/08/04/1	mailing-listx_refsource_MLIST
http://www.securityfocus.com/bid/92195	vdb-entryx_refsource_BID
http://www.securitytracker.com/id/1036548	vdb-entryx_refsource_SECTRACK
http://www.openwall.com/lists/oss-security/2016/09/02/1	mailing-listx_refsource_MLIST

Date Public

2016-08-04 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-06T01:36:28.441Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "[oss-security] 20160902 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
            "tags": [
              "mailing-list",
              "x_refsource_MLIST",
              "x_transferred"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
          },
          {
            "name": "[oss-security] 20160804 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
            "tags": [
              "mailing-list",
              "x_refsource_MLIST",
              "x_transferred"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
          },
          {
            "name": "92195",
            "tags": [
              "vdb-entry",
              "x_refsource_BID",
              "x_transferred"
            ],
            "url": "http://www.securityfocus.com/bid/92195"
          },
          {
            "name": "1036548",
            "tags": [
              "vdb-entry",
              "x_refsource_SECTRACK",
              "x_transferred"
            ],
            "url": "http://www.securitytracker.com/id/1036548"
          },
          {
            "name": "[oss-security] 20160901 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
            "tags": [
              "mailing-list",
              "x_refsource_MLIST",
              "x_transferred"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2016-08-04T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-08-15T09:57:01.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "name": "[oss-security] 20160902 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
          "tags": [
            "mailing-list",
            "x_refsource_MLIST"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
        },
        {
          "name": "[oss-security] 20160804 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
          "tags": [
            "mailing-list",
            "x_refsource_MLIST"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
        },
        {
          "name": "92195",
          "tags": [
            "vdb-entry",
            "x_refsource_BID"
          ],
          "url": "http://www.securityfocus.com/bid/92195"
        },
        {
          "name": "1036548",
          "tags": [
            "vdb-entry",
            "x_refsource_SECTRACK"
          ],
          "url": "http://www.securitytracker.com/id/1036548"
        },
        {
          "name": "[oss-security] 20160901 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
          "tags": [
            "mailing-list",
            "x_refsource_MLIST"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
        }
      ],
      "tags": [
        "disputed"
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2016-6595",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "** DISPUTED ** 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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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.\""
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "[oss-security] 20160902 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
              "refsource": "MLIST",
              "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
            },
            {
              "name": "[oss-security] 20160804 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
              "refsource": "MLIST",
              "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
            },
            {
              "name": "92195",
              "refsource": "BID",
              "url": "http://www.securityfocus.com/bid/92195"
            },
            {
              "name": "1036548",
              "refsource": "SECTRACK",
              "url": "http://www.securitytracker.com/id/1036548"
            },
            {
              "name": "[oss-security] 20160901 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
              "refsource": "MLIST",
              "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2016-6595",
    "datePublished": "2017-01-04T20:00:00.000Z",
    "dateReserved": "2016-08-03T00:00:00.000Z",
    "dateUpdated": "2024-08-06T01:36:28.441Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2016-6595",
      "date": "2026-11-06",
      "epss": "0.0282",
      "percentile": "0.86633"
    },
    "fkie_nvd": {
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:docker:docker:1.12.0:*:*:*:*:*:*:*",
                  "matchCriteriaId": "23E0746F-B8B4-4B66-A540-9447B4690F14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [
        {
          "sourceIdentifier": "cve@mitre.org",
          "tags": [
            "disputed"
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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."
        },
        {
          "lang": "es",
          "value": "** DISPUTADA ** El SwarmKit toolkit 1.12.0 para Docker permite a usuarios remotos autenticados provocar una denegaci\u00f3n de servicio (prevenci\u00f3n de entradas de cluster) a trav\u00e9s de una secuencia larga de acciones de entrada y salida. NOTA: el vendedor cuestiona este problema, afirmando que esta secuencia no \"elimina el estado que dejan los nodos anteriores. En alg\u00fan momento el administrador obviamente deja de ser capaz de aceptar nodos nuevos, ya que se le acaba la memoria. Ya que los nodos tanto de Docker swarm y Docker Swarmkit son \"necesarios* para proporcionar un token secreto (en realidad es el \u00fanico modo de operaci\u00f3n), esto significa que ning\u00fan adversario puede unir simplemente los nodos y agotar los recursos del administrador. No podemos hacer nada acerca de la p\u00e9rdida de memoria de un administrador y la incapacidad de a\u00f1adir nuevos nodos leg\u00edtimos al sistema. Esto es simplemente un problema de aprovisionamiento de recursos y no una vulnerabilidad merecedora de una CVE\"."
        }
      ],
      "id": "CVE-2016-6595",
      "lastModified": "2024-11-21T02:56:24.230",
      "metrics": {
        "cvssMetricV2": [
          {
            "acInsufInfo": true,
            "baseSeverity": "MEDIUM",
            "cvssData": {
              "accessComplexity": "LOW",
              "accessVector": "NETWORK",
              "authentication": "SINGLE",
              "availabilityImpact": "PARTIAL",
              "baseScore": 4.0,
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "vectorString": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
              "version": "2.0"
            },
            "exploitabilityScore": 8.0,
            "impactScore": 2.9,
            "obtainAllPrivilege": false,
            "obtainOtherPrivilege": false,
            "obtainUserPrivilege": false,
            "source": "nvd@nist.gov",
            "type": "Primary",
            "userInteractionRequired": false
          }
        ],
        "cvssMetricV30": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 6.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.0"
            },
            "exploitabilityScore": 2.8,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      },
      "published": "2017-01-04T20:59:00.247",
      "references": [
        {
          "source": "cve@mitre.org",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
        },
        {
          "source": "cve@mitre.org",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
        },
        {
          "source": "cve@mitre.org",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
        },
        {
          "source": "cve@mitre.org",
          "url": "http://www.securityfocus.com/bid/92195"
        },
        {
          "source": "cve@mitre.org",
          "url": "http://www.securitytracker.com/id/1036548"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "url": "http://www.securityfocus.com/bid/92195"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "url": "http://www.securitytracker.com/id/1036548"
        }
      ],
      "sourceIdentifier": "cve@mitre.org",
      "vulnStatus": "Modified",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-399"
            }
          ],
          "source": "nvd@nist.gov",
          "type": "Primary"
        }
      ]
    },
    "nvd": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:docker:docker:1.12.0:*:*:*:*:*:*:*",
                    "matchCriteriaId": "23E0746F-B8B4-4B66-A540-9447B4690F14",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [
          {
            "sourceIdentifier": "cve@mitre.org",
            "tags": [
              "disputed"
            ]
          }
        ],
        "descriptions": [
          {
            "lang": "en",
            "value": "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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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."
          },
          {
            "lang": "es",
            "value": "** DISPUTADA ** El SwarmKit toolkit 1.12.0 para Docker permite a usuarios remotos autenticados provocar una denegaci\u00f3n de servicio (prevenci\u00f3n de entradas de cluster) a trav\u00e9s de una secuencia larga de acciones de entrada y salida. NOTA: el vendedor cuestiona este problema, afirmando que esta secuencia no \"elimina el estado que dejan los nodos anteriores. En alg\u00fan momento el administrador obviamente deja de ser capaz de aceptar nodos nuevos, ya que se le acaba la memoria. Ya que los nodos tanto de Docker swarm y Docker Swarmkit son \"necesarios* para proporcionar un token secreto (en realidad es el \u00fanico modo de operaci\u00f3n), esto significa que ning\u00fan adversario puede unir simplemente los nodos y agotar los recursos del administrador. No podemos hacer nada acerca de la p\u00e9rdida de memoria de un administrador y la incapacidad de a\u00f1adir nuevos nodos leg\u00edtimos al sistema. Esto es simplemente un problema de aprovisionamiento de recursos y no una vulnerabilidad merecedora de una CVE\"."
          }
        ],
        "id": "CVE-2016-6595",
        "lastModified": "2026-05-06T22:30:45.220",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": true,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "LOW",
                "accessVector": "NETWORK",
                "authentication": "SINGLE",
                "availabilityImpact": "PARTIAL",
                "baseScore": 4.0,
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "vectorString": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
                "version": "2.0"
              },
              "exploitabilityScore": 8.0,
              "impactScore": 2.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": false
            }
          ],
          "cvssMetricV30": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.0"
              },
              "exploitabilityScore": 2.8,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2017-01-04T20:59:00.247",
        "references": [
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
          },
          {
            "source": "cve@mitre.org",
            "url": "http://www.securityfocus.com/bid/92195"
          },
          {
            "source": "cve@mitre.org",
            "url": "http://www.securitytracker.com/id/1036548"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "url": "http://www.securityfocus.com/bid/92195"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "url": "http://www.securitytracker.com/id/1036548"
          }
        ],
        "sourceIdentifier": "cve@mitre.org",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-399"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-06T09:48:40+00:00",
      "cve": "CVE-2016-6595",
      "id": "CVE-2016-6595",
      "initial_release_date": "2016-07-29T00:00:00+00:00",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "10",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "docker: DoS via repeatedly joining and quitting swarm cluster as a node",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2016/cve-2016-6595.json",
      "version": "3"
    }
  }
}

CNVD-2017-00178

Vulnerability from cnvd - Published: 2017-01-06

Title

Docker Swarmki本地拒绝服务漏洞

Description

Docker是美国Docker公司的一款开源的应用容器引擎，它支持在Linux系统上创建一个容器（轻量级虚拟机）并部署和运行应用程序，以及通过配置文件实现应用程序的自动化安装、部署和升级。 Docker Swarmki存在本地拒绝服务漏洞。本地攻击者可以利用漏洞导致主机挂起，拒绝为合法用户提供服务。

Severity

低

Formal description

目前厂商暂未发布修复措施解决此安全问题，建议使用此软件的用户随时关注厂商主页或参考网址以获取解决办法： https://github.com/docker/swarmkit

Reference

http://www.securityfocus.com/bid/92195

Impacted products

Name
Docker Swarmkit 1.12

Show details on source website

JSON

To clipboard

{
  "bids": {
    "bid": {
      "bidNumber": "92195"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-6595",
      "cveUrl": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6595"
    }
  },
  "description": "Docker\u662f\u7f8e\u56fdDocker\u516c\u53f8\u7684\u4e00\u6b3e\u5f00\u6e90\u7684\u5e94\u7528\u5bb9\u5668\u5f15\u64ce\uff0c\u5b83\u652f\u6301\u5728Linux\u7cfb\u7edf\u4e0a\u521b\u5efa\u4e00\u4e2a\u5bb9\u5668\uff08\u8f7b\u91cf\u7ea7\u865a\u62df\u673a\uff09\u5e76\u90e8\u7f72\u548c\u8fd0\u884c\u5e94\u7528\u7a0b\u5e8f\uff0c\u4ee5\u53ca\u901a\u8fc7\u914d\u7f6e\u6587\u4ef6\u5b9e\u73b0\u5e94\u7528\u7a0b\u5e8f\u7684\u81ea\u52a8\u5316\u5b89\u88c5\u3001\u90e8\u7f72\u548c\u5347\u7ea7\u3002\r\n                                                                                   Docker Swarmki\u5b58\u5728\u672c\u5730\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u4ee5\u5229\u7528\u6f0f\u6d1e\u5bfc\u81f4\u4e3b\u673a\u6302\u8d77\uff0c\u62d2\u7edd\u4e3a\u5408\u6cd5\u7528\u6237\u63d0\u4f9b\u670d\u52a1\u3002",
  "discovererName": "zhangkaixiang",
  "formalWay": "\u76ee\u524d\u5382\u5546\u6682\u672a\u53d1\u5e03\u4fee\u590d\u63aa\u65bd\u89e3\u51b3\u6b64\u5b89\u5168\u95ee\u9898\uff0c\u5efa\u8bae\u4f7f\u7528\u6b64\u8f6f\u4ef6\u7684\u7528\u6237\u968f\u65f6\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u6216\u53c2\u8003\u7f51\u5740\u4ee5\u83b7\u53d6\u89e3\u51b3\u529e\u6cd5\uff1a\r\nhttps://github.com/docker/swarmkit",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-00178",
  "openTime": "2017-01-06",
  "products": {
    "product": "Docker Swarmkit  1.12"
  },
  "referenceLink": "http://www.securityfocus.com/bid/92195",
  "serverity": "\u4f4e",
  "submitTime": "2017-01-05",
  "title": "Docker Swarmki\u672c\u5730\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e"
}

FKIE_CVE-2016-6595

Vulnerability from fkie_nvd - Published: 2017-01-04 20:59 - Updated: 2026-06-17 00:51

Severity

6.5 (Medium) - CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Summary

References

URL	Tags
cve@mitre.org	http://www.openwall.com/lists/oss-security/2016/08/04/1	Third Party Advisory
cve@mitre.org	http://www.openwall.com/lists/oss-security/2016/09/02/1	Third Party Advisory
cve@mitre.org	http://www.openwall.com/lists/oss-security/2016/09/02/8	Third Party Advisory
cve@mitre.org	http://www.securityfocus.com/bid/92195
cve@mitre.org	http://www.securitytracker.com/id/1036548
af854a3a-2127-422b-91ae-364da2661108	http://www.openwall.com/lists/oss-security/2016/08/04/1	Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108	http://www.openwall.com/lists/oss-security/2016/09/02/1	Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108	http://www.openwall.com/lists/oss-security/2016/09/02/8	Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108	http://www.securityfocus.com/bid/92195
af854a3a-2127-422b-91ae-364da2661108	http://www.securitytracker.com/id/1036548

Impacted products

	Vendor	Product	Version
	docker	docker	1.12.0

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "source": "cve@mitre.org"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:docker:docker:1.12.0:*:*:*:*:*:*:*",
              "matchCriteriaId": "23E0746F-B8B4-4B66-A540-9447B4690F14",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [
    {
      "sourceIdentifier": "cve@mitre.org",
      "tags": [
        "disputed"
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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."
    },
    {
      "lang": "es",
      "value": "** DISPUTADA ** El SwarmKit toolkit 1.12.0 para Docker permite a usuarios remotos autenticados provocar una denegaci\u00f3n de servicio (prevenci\u00f3n de entradas de cluster) a trav\u00e9s de una secuencia larga de acciones de entrada y salida. NOTA: el vendedor cuestiona este problema, afirmando que esta secuencia no \"elimina el estado que dejan los nodos anteriores. En alg\u00fan momento el administrador obviamente deja de ser capaz de aceptar nodos nuevos, ya que se le acaba la memoria. Ya que los nodos tanto de Docker swarm y Docker Swarmkit son \"necesarios* para proporcionar un token secreto (en realidad es el \u00fanico modo de operaci\u00f3n), esto significa que ning\u00fan adversario puede unir simplemente los nodos y agotar los recursos del administrador. No podemos hacer nada acerca de la p\u00e9rdida de memoria de un administrador y la incapacidad de a\u00f1adir nuevos nodos leg\u00edtimos al sistema. Esto es simplemente un problema de aprovisionamiento de recursos y no una vulnerabilidad merecedora de una CVE\"."
    }
  ],
  "id": "CVE-2016-6595",
  "lastModified": "2026-06-17T00:51:25.510",
  "metrics": {
    "cvssMetricV2": [
      {
        "acInsufInfo": true,
        "baseSeverity": "MEDIUM",
        "cvssData": {
          "accessComplexity": "LOW",
          "accessVector": "NETWORK",
          "authentication": "SINGLE",
          "availabilityImpact": "PARTIAL",
          "baseScore": 4.0,
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "vectorString": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
          "version": "2.0"
        },
        "exploitabilityScore": 8.0,
        "impactScore": 2.9,
        "obtainAllPrivilege": false,
        "obtainOtherPrivilege": false,
        "obtainUserPrivilege": false,
        "source": "nvd@nist.gov",
        "type": "Primary",
        "userInteractionRequired": false
      }
    ],
    "cvssMetricV30": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 6.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.0"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 3.6,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2017-01-04T20:59:00.247",
  "references": [
    {
      "source": "cve@mitre.org",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
    },
    {
      "source": "cve@mitre.org",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
    },
    {
      "source": "cve@mitre.org",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
    },
    {
      "source": "cve@mitre.org",
      "url": "http://www.securityfocus.com/bid/92195"
    },
    {
      "source": "cve@mitre.org",
      "url": "http://www.securitytracker.com/id/1036548"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://www.securityfocus.com/bid/92195"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://www.securitytracker.com/id/1036548"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-399"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}

GHSA-669G-G3V8-296M

Vulnerability from github – Published: 2022-05-17 02:13 – Updated: 2022-05-17 02:13

Details

** DISPUTED ** 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."

Severity

6.5 (Medium)


                  
                    CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2016-6595"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2017-01-04T20:59:00Z",
    "severity": "MODERATE"
  },
  "details": "** DISPUTED ** 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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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.\"",
  "id": "GHSA-669g-g3v8-296m",
  "modified": "2022-05-17T02:13:04Z",
  "published": "2022-05-17T02:13:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-6595"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/92195"
    },
    {
      "type": "WEB",
      "url": "http://www.securitytracker.com/id/1036548"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GSD-2016-6595

Vulnerability from gsd - Updated: 2023-12-13 01:21

Details

** DISPUTED ** 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."

Aliases

CVE-2016-6595

Aliases

CVE-2016-6595

JSON

To clipboard

{
  "GSD": {
    "alias": "CVE-2016-6595",
    "description": "** DISPUTED ** 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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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.\"",
    "id": "GSD-2016-6595"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2016-6595"
      ],
      "details": "** DISPUTED ** 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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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.\"",
      "id": "GSD-2016-6595",
      "modified": "2023-12-13T01:21:22.969995Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "cve@mitre.org",
        "ID": "CVE-2016-6595",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "n/a",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "n/a"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "** DISPUTED ** 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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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.\""
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "n/a"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "[oss-security] 20160902 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
            "refsource": "MLIST",
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
          },
          {
            "name": "[oss-security] 20160804 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
            "refsource": "MLIST",
            "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
          },
          {
            "name": "92195",
            "refsource": "BID",
            "url": "http://www.securityfocus.com/bid/92195"
          },
          {
            "name": "1036548",
            "refsource": "SECTRACK",
            "url": "http://www.securitytracker.com/id/1036548"
          },
          {
            "name": "[oss-security] 20160901 Re: cve request: docker swarmkit Dos occurs by repeatly joining and quitting swam cluster as a node",
            "refsource": "MLIST",
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
          }
        ]
      }
    },
    "nvd.nist.gov": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:docker:docker:1.12.0:*:*:*:*:*:*:*",
                    "matchCriteriaId": "23E0746F-B8B4-4B66-A540-9447B4690F14",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "descriptions": [
          {
            "lang": "en",
            "value": "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\u0027s actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can\u0027t 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."
          },
          {
            "lang": "es",
            "value": "** DISPUTADA ** El SwarmKit toolkit 1.12.0 para Docker permite a usuarios remotos autenticados provocar una denegaci\u00f3n de servicio (prevenci\u00f3n de entradas de cluster) a trav\u00e9s de una secuencia larga de acciones de entrada y salida. NOTA: el vendedor cuestiona este problema, afirmando que esta secuencia no \"elimina el estado que dejan los nodos anteriores. En alg\u00fan momento el administrador obviamente deja de ser capaz de aceptar nodos nuevos, ya que se le acaba la memoria. Ya que los nodos tanto de Docker swarm y Docker Swarmkit son \"necesarios* para proporcionar un token secreto (en realidad es el \u00fanico modo de operaci\u00f3n), esto significa que ning\u00fan adversario puede unir simplemente los nodos y agotar los recursos del administrador. No podemos hacer nada acerca de la p\u00e9rdida de memoria de un administrador y la incapacidad de a\u00f1adir nuevos nodos leg\u00edtimos al sistema. Esto es simplemente un problema de aprovisionamiento de recursos y no una vulnerabilidad merecedora de una CVE\"."
          }
        ],
        "id": "CVE-2016-6595",
        "lastModified": "2024-04-11T00:56:06.217",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": true,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "LOW",
                "accessVector": "NETWORK",
                "authentication": "SINGLE",
                "availabilityImpact": "PARTIAL",
                "baseScore": 4.0,
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "vectorString": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
                "version": "2.0"
              },
              "exploitabilityScore": 8.0,
              "impactScore": 2.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": false
            }
          ],
          "cvssMetricV30": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.0"
              },
              "exploitabilityScore": 2.8,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2017-01-04T20:59:00.247",
        "references": [
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/08/04/1"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/1"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2016/09/02/8"
          },
          {
            "source": "cve@mitre.org",
            "url": "http://www.securityfocus.com/bid/92195"
          },
          {
            "source": "cve@mitre.org",
            "url": "http://www.securitytracker.com/id/1036548"
          }
        ],
        "sourceIdentifier": "cve@mitre.org",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-399"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    }
  }
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CVE-2016-6595 (GCVE-0-2016-6595)

CNVD-2017-00178

FKIE_CVE-2016-6595

GHSA-669G-G3V8-296M

GSD-2016-6595

Tags

Sightings

Nomenclature

Vulnerability timeline

Related by attack behaviour