CVE-2016-6580
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | priority | <1.2.0 | 1.2.0 |
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| 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/92311
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html
- https://nvd.nist.gov/vuln/detail/CVE-2016-6580
- https://github.com/python-hyper/priority/commit/7d01a7dc4db83bce50f20d47caf4f37b403a3ecd
- https://github.com/pypa/advisory-database/tree/main/vulns/priority/PYSEC-2017-93.yaml
- https://github.com/python-hyper/priority
- https://web.archive.org/web/20160806004329/http://www.securityfocus.com/bid/92311
CWEs
CWE-399
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.