CVE-2016-6580
Last modified
CVE-2016-6580 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.79% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Python | Python Priority Library | 1.0.0 |
| Python | Python Priority Library | 1.1.0 |
| Python | Python Priority Library | 1.1.1 |
References
- http://www.securityfocus.com/bid/92311Third Party Advisory, VDB Entry
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.htmlMitigation, Vendor Advisory
- http://www.securityfocus.com/bid/92311Third Party Advisory, VDB Entry
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.htmlMitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-6580?
How severe is CVE-2016-6580?
How do I fix CVE-2016-6580?
Are you affected by CVE-2016-6580?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
