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.
References
Link Resource
http://www.securityfocus.com/bid/92311 Third Party Advisory VDB Entry
https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html Mitigation Vendor Advisory
History

No history.

cve-icon MITRE Information

Status: PUBLISHED

Assigner: mitre

Published: 2017-01-10T15:00:00

Updated: 2017-01-11T13:57:01

Reserved: 2016-08-03T00:00:00


Link: CVE-2016-6580

JSON object: View

cve-icon NVD Information

Status : Analyzed

Published: 2017-01-10T15:59:00.377

Modified: 2017-01-27T19:42:26.527


Link: CVE-2016-6580

JSON object: View

cve-icon Redhat Information

No data.

CWE