PYSEC-2017-93
Vulnerability from pysec - Published: 2017-01-10 15:59 - Updated: 2021-08-27 03:22A 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.
| Name | purl | priority | pkg:pypi/priority |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "priority",
"purl": "pkg:pypi/priority"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.0.1",
"1.0.0",
"1.1.0",
"1.1.1"
]
}
],
"aliases": [
"CVE-2016-6580",
"GHSA-h3q4-6j7f-r24c"
],
"details": "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.",
"id": "PYSEC-2017-93",
"modified": "2021-08-27T03:22:16.246169Z",
"published": "2017-01-10T15:59:00Z",
"references": [
{
"type": "WEB",
"url": "https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/92311"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-h3q4-6j7f-r24c"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.