Approved changes feed: RSS · Atom

cpe:2.3:a:python:python_priority_library:1.1.1:*:*:*:*:*:*:*

part: a version: 1.1.1 update: *

VendorPython (b57ad93a-6195-5192-9423-6cfad6044a8b)
ProductPython Priority Library (06acaade-7333-56e8-a866-2d838fefe014)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/python-priority purl2cpe 2026-06-01 10:16:28.915739
pkg:deb/ubuntu/python-priority purl2cpe 2026-06-01 10:16:28.915740
pkg:github/python-hyper/priority purl2cpe 2026-06-01 10:16:28.915741
pkg:pypi/priority purl2cpe 2026-06-01 10:16:28.915743
pkg:rpm/fedora/python-priority purl2cpe 2026-06-01 10:16:28.915744
pkg:rpm/opensuse/python-priority purl2cpe 2026-06-01 10:16:28.915746

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2016-6580 vulnerable 2026-06-03 14:36:00.722073 Details available
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-10T15:00:00.000Z
Updated: 2024-08-06T01:36:28.170Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.