AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655044

http://mail.gnome.org/archives/gtk-devel-list/2003-May/msg00111.html

http://openwall.com/lists/oss-security/2012/01/10/12

https://bugzilla.redhat.com/show_bug.cgi?id=772720

Red Hat, Inc. disputed

** DISPUTED ** 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.

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.

** DISPUTED ** 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.

** DISPUTED ** 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.

** DISPUTADA ** GLib 2.31.8 y anteriores, cuando la función g_str_hash está utilizada, calcula los valores hash sin restringir la capacidad de provocar colisiones previsibles, lo que permite a atacantes dependientes de contexto causar una denegación de servicio (consumo de CPU) a través de entradas manipuladas en una aplicación que mantiene una tabla hash. NOTA: este problema lo puede disputar el proveedor, la existencia de la función g_str_hash no se tarta de una vulnerabilidad en la librería, porque llamadores de g_hash_table_new y g_hash_table_new_full pueden especificar una función hash arbitraria que sea apropiada para la aplicación.

GLib v2.31.8 y anteriores, cuando se utiliza la funcion g_str_hash, calcula valores hash  que podrían generar colisiones, permitiendo a atacantes dependientes de contexto  causar una denegación de servicio (consumo de CPU) a través del envío de entradas (inputs) especialmente manipuladas a una aplicación que mantiene una tabla hash. NOTA: la existencia de la función g_str_hash no es una vulnerabilidad en la librería,  llamadas de g_hash_table_new y g_hash_table_new_full puede especificar una función arbitraria hash que sea apropiada para la aplicación.