GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.
-
Package | Type | OS Name | OS Version | Affected Ranges | Fix Versions |
---|---|---|---|---|---|
debian/glib2.0 | deb | debian | 12 | >=2.74.6-2 | Not yet available |
debian/glib2.0 | deb | debian | unstable | >=2.80.2-1 | Not yet available |
debian/glib2.0 | deb | debian | 11 | >=2.66.8-1+deb11u1 | Not yet available |
debian/glib2.0 | deb | debian | 10 | >=2.58.3-2+deb10u3 | Not yet available |
debian/glib2.0 | deb | debian | 13 | >=2.80.2-1 | Not yet available |
Severity and metrics
No CVSS data available from this source.
10
-
10.0