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
CVSS 3.0 7.5/10
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
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
- Jan 10, 2017
- Last modified
- Jun 17, 2026
- NVD status
- Modified