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.
No summary for this CVE yet.
CVSS Vector Breakdown
Exploitability
AV:NAttack VectorNetwork
AC:LAttack ComplexityLow
PR:NPrivileges RequiredNone
UI:NUser InteractionNone
Scope
S:UScopeUnchanged
Impact
C:NConfidentialityNone
I:NIntegrityNone
A:HAvailabilityHigh
Weaknesses
Affected Products
PyPI
package-ecosystem
python
oss-project·US
and 1 more affected products View all →
Exploitability
Official Patch Available
Workaround Available
References
http://www.securityfocus.com/bid/92311
securityfocus.com
https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html
python-hyper.org
https://nvd.nist.gov/vuln/detail/CVE-2016-6580
nvd.nist.gov
and 10 more references View all →
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2016-6580 and every CVE in our database. Create a free account — no credit card required.
Create Free AccountPlain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows