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.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

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

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

Link: CVE-2016-6580

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

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

Modified: 2025-04-20T01:37:25.860

Link: CVE-2016-6580

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.