CVE-2016-6580

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

NeevaHost hosting service

Configurations

Configuration 1 (hide)

OR cpe:2.3:a:python:python_priority_library:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:python:python_priority_library:1.1.0:*:*:*:*:*:*:*
cpe:2.3:a:python:python_priority_library:1.1.1:*:*:*:*:*:*:*

Information

Published : 2017-01-10 07:59

Updated : 2017-01-27 11:42


NVD link : CVE-2016-6580

Mitre link : CVE-2016-6580


JSON object : View

CWE
CWE-399

Resource Management Errors

Advertisement

dedicated server usa

Products Affected

python

  • python_priority_library