Description
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.
Published: 2017-01-10
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2017-0099 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.
Github GHSA Github GHSA GHSA-h3q4-6j7f-r24c priority vulnerable to denial of service
History

No history.

Subscriptions

Python Python Priority Library
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-06T01:36:28.170Z

Reserved: 2016-08-03T00:00:00.000Z

Link: CVE-2016-6580

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2017-01-10T15:59:00.377

Modified: 2026-05-06T22:30:45.220

Link: CVE-2016-6580

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses