Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Python | Python Priority Library | 1.0.0 |
Related Weaknesses (CWE)
References
- http://www.securityfocus.com/bid/92311Third Party AdvisoryVDB Entry
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.htmlMitigationVendor Advisory
- http://www.securityfocus.com/bid/92311Third Party AdvisoryVDB Entry
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.htmlMitigationVendor Advisory
FAQ
What is CVE-2016-6580?
CVE-2016-6580 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 po...
How severe is CVE-2016-6580?
CVE-2016-6580 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2016-6580?
Check the references section above for vendor advisories and patch information. Affected products include: Python Python Priority Library.