Id:
CVE-2016-6580
Comment
:
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.
CVSSv2 Score:
5
Access vector:
|
NETWORK
|
Access complexity:
|
LOW
|
Authentication:
|
NONE
|
Confidentiality impact:
|
NONE
|
Integrity impact:
|
NONE
|
Availability impact:
|
PARTIAL
|
CVSSv2 Vector:
AV:N/AC:L/Au:N/C:N/I:N/A:P
CVSSv3 Score:
7.5
Attack vector:
|
NETWORK
|
Attack complexity:
|
LOW
|
Privileges required:
|
NONE
|
User interaction:
|
NONE
|
Scope:
|
UNCHANGED
|
Confidentiality impact:
|
NONE
|
Integrity impact:
|
NONE
|
Availability impact:
|
HIGH
|
CVSSv3 Vector:
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References: