priority vulnerable to denial of service
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-6580US | high7.5 | — | ||
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 info… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/pypa/advisory-database/tree/main/vulns/priority/PYSEC-2017-93.yamlWEB
- https://github.com/python-hyper/priorityPACKAGE
- https://github.com/python-hyper/priority/commit/7d01a7dc4db83bce50f20d47caf4f37b403a3ecdWEB
- https://nvd.nist.gov/vuln/detail/CVE-2016-6580ADVISORY
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.htmlWEB
- https://web.archive.org/web/20160806004329/http://www.securityfocus.com/bid/92311WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan