CVE-2016-6580
First published: Tue Jan 10 2017(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/priority | >=0<1.2.0 | 1.2.0 |
| Python Priority Library | =1.0.0 | |
| Python Priority Library | =1.1.0 | |
| Python Priority Library | =1.1.1 | |
| =1.0.0 | ||
| =1.1.0 | ||
| =1.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/92311
- https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html
- https://nvd.nist.gov/vuln/detail/CVE-2016-6580
- https://github.com/python-hyper/priority/commit/7d01a7dc4db83bce50f20d47caf4f37b403a3ecd
- https://github.com/pypa/advisory-database/tree/main/vulns/priority/PYSEC-2017-93.yaml
- https://web.archive.org/web/20160806004329/http://www.securityfocus.com/bid/92311
- https://github.com/advisories/GHSA-h3q4-6j7f-r24c (Advisory)
Frequently Asked Questions
What is the severity of CVE-2016-6580?
CVE-2016-6580 is considered a medium severity vulnerability due to its potential impact on application performance and stability.
How do I fix CVE-2016-6580?
To fix CVE-2016-6580, update the Python priority library to version 1.2.0 or later.
What software is affected by CVE-2016-6580?
CVE-2016-6580 affects all versions of the Python priority library prior to 1.2.0.
Can CVE-2016-6580 be exploited remotely?
Yes, CVE-2016-6580 can potentially be exploited by a malicious peer over the network.
What are the risks of not addressing CVE-2016-6580?
Failing to address CVE-2016-6580 may lead to degraded application performance and possible denial of service.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-h3q4-6j7f-r24c
- alias/CVE-2016-6580
- agent/software-canonical-lookup
- agent/references
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/event
- agent/author
- collector/github-advisory
- agent/trending
- agent/source
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- source/NVD
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- package-manager/pip
- vendor/python
- canonical/python priority library
- version/python priority library/1.0.0
- version/python priority library/1.1.0
- version/python priority library/1.1.1