{"id":"CVE-2016-6580","published":"2017-01-10T15:00:00Z","modified":"2024-08-06T01:36:28Z","title":"A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could be…","vendor":null,"product":null,"tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.01842,"percentile":0.7953,"provenance":"source"},"cwes":[],"references":[{"url":"http://www.securityfocus.com/bid/92311","tags":["vdb-entry","x_refsource_BID"]},{"url":"https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html","tags":["x_refsource_CONFIRM"]}],"priority":{"score":15.9,"factors":[{"name":"EPSS percentile","points":15.91}]},"affected":[{"ecosystem":"PyPI","package":"priority","vulnerableRanges":["<1.2.0"],"patched":["1.2.0"],"from":["GHSA-h3q4-6j7f-r24c","PYSEC-2017-93"],"provenance":"source"}],"summary":{"text":"The flaw affects HTTP/2 implementations built on the Python priority library before version 1.2.0, where stream priority information is stored in a priority tree. An attacker acting as a malicious peer can assign priority information for every possible HTTP/2 stream ID, causing unbounded memory allocation and very high CPU usage as the tree is maintained.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:39:19Z"},"euvd":{"id":"EUVD-2017-0099","exploited":false,"provenance":"source"}}