Safety vulnerability ID: 35679
The information on this page was manually curated by our Cybersecurity Intelligence Team.
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.
Latest version: 4.0.0
Pure-Python HPACK header compression
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.
CONFIRM:https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html: https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html
BID:92311: http://www.securityfocus.com/bid/92311
Scan your Python project for dependency vulnerabilities in two minutes
Scan your application