CVE-2016-6580
Apache Priority HTTP/2 Denial of Service
Description
A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could be targeted by a malicious peer by having that peer assign priority information for every possible HTTP/2 stream ID. The priority tree would happily continue to store the priority information for each stream, and would therefore allocate unbounded amounts of memory. Attempting to actually use a tree like this would also cause extremely high CPU usage to maintain the tree.
INFO
Published Date :
Jan. 10, 2017, 3:59 p.m.
Last Modified :
Jan. 27, 2017, 7:42 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
3.9
Affected Products
The following products are affected by CVE-2016-6580
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2016-6580.
| URL | Resource |
|---|---|
| http://www.securityfocus.com/bid/92311 | Third Party Advisory VDB Entry |
| https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html | Mitigation Vendor Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2016-6580 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2016-6580 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Modified Analysis by [email protected]
Jan. 27, 2017
Action Type Old Value New Value Changed CPE Configuration OR *cpe:2.3:a:python_software_foundation:python_priority_library:1.0.0:*:*:*:*:*:*:* *cpe:2.3:a:python_software_foundation:python_priority_library:1.1.0:*:*:*:*:*:*:* *cpe:2.3:a:python_software_foundation:python_priority_library:1.1.1:*:*:*:*:*:*:* OR *cpe:2.3:a:python:python_priority_library:1.0.0:*:*:*:*:*:*:* *cpe:2.3:a:python:python_priority_library:1.1.0:*:*:*:*:*:*:* *cpe:2.3:a:python:python_priority_library:1.1.1:*:*:*:*:*:*:* -
CVE Modified by [email protected]
Jan. 13, 2017
Action Type Old Value New Value Changed Description A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could be targetted by a malicious peer by having that peer assign priority information for every possible HTTP/2 stream ID. The priority tree would happily continue to store the priority information for each stream, and would therefore allocate unbounded amounts of memory. Attempting to actually use a tree like this would also cause extremely high CPU usage to maintain the tree. A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could be targeted by a malicious peer by having that peer assign priority information for every possible HTTP/2 stream ID. The priority tree would happily continue to store the priority information for each stream, and would therefore allocate unbounded amounts of memory. Attempting to actually use a tree like this would also cause extremely high CPU usage to maintain the tree. -
Initial Analysis by [email protected]
Jan. 11, 2017
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:L/Au:N/C:N/I:N/A:P) Added CVSS V3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Changed Reference Type http://www.securityfocus.com/bid/92311 No Types Assigned http://www.securityfocus.com/bid/92311 Third Party Advisory, VDB Entry Changed Reference Type https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html No Types Assigned https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html Mitigation, Vendor Advisory Added CWE CWE-399 Added CPE Configuration OR *cpe:2.3:a:python_software_foundation:python_priority_library:1.0.0:*:*:*:*:*:*:* *cpe:2.3:a:python_software_foundation:python_priority_library:1.1.0:*:*:*:*:*:*:* *cpe:2.3:a:python_software_foundation:python_priority_library:1.1.1:*:*:*:*:*:*:*
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2016-6580 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2016-6580
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.10 }} 0.00%
score
0.38726
percentile