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
Affected Vendors & Products
References
History
No history.

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-06T01:36:28.170Z
Reserved: 2016-08-03T00:00:00
Link: CVE-2016-6580

No data.

Status : Modified
Published: 2017-01-10T15:59:00.377
Modified: 2024-11-21T02:56:22.577
Link: CVE-2016-6580

No data.