| CVE-2016-6580 | Date: (C)2017-01-11 (M)2023-12-22 |
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.
CVSS Score and Metrics +CVSS Score and Metrics -| CVSS V3 Severity: | CVSS V2 Severity: |
| CVSS Score : 7.5 | CVSS Score : 5.0 |
| Exploit Score: 3.9 | Exploit Score: 10.0 |
| Impact Score: 3.6 | Impact Score: 2.9 |
| |
| CVSS V3 Metrics: | CVSS V2 Metrics: |
| Attack Vector: NETWORK | Access Vector: NETWORK |
| Attack Complexity: LOW | Access Complexity: LOW |
| Privileges Required: NONE | Authentication: NONE |
| User Interaction: NONE | Confidentiality: NONE |
| Scope: UNCHANGED | Integrity: NONE |
| Confidentiality: NONE | Availability: PARTIAL |
| Integrity: NONE | |
| Availability: HIGH | |
| | |
