CVE-2016-6580

UnknownEPSS 1.79%

Last modified

CVE-2016-6580 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.79% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
1.79%

75.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PythonPython Priority Library1.0.0
PythonPython Priority Library1.1.0
PythonPython Priority Library1.1.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-6580?
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.
How severe is CVE-2016-6580?
Severity scoring for CVE-2016-6580 is pending analysis. The EPSS model estimates a 1.79% probability of exploitation in the next 30 days.
How do I fix CVE-2016-6580?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-6580?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST