Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2012-0039

Publication date 14 January 2012

Last updated 24 July 2024

Ubuntu priority

Low

Why this priority?

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

Read the notes from the security team

Status

Package Ubuntu Release Status
glib2.0 19.04 disco Ignored
18.10 cosmic Ignored
18.04 LTS bionic Ignored
17.10 artful Ignored end of life
17.04 zesty Ignored end of life
16.10 yakkety Ignored end of life
16.04 LTS xenial Ignored
15.10 wily Ignored end of life
15.04 vivid Ignored end of life
14.10 utopic Ignored end of life
14.04 LTS trusty Ignored
13.10 saucy Ignored end of life
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Ignored end of life
11.10 oneiric Ignored end of life
11.04 natty Ignored end of life
10.10 maverick Ignored end of life
10.04 LTS lucid Ignored end of life
8.04 LTS hardy Ignored end of life

Notes

mdeslaur

as of 2012-02-21, upstream has simply added a warning: http://git.gnome.org/browse/glib/commit/?id=030b3f25e3e5c018247e18bf309e0454ba138898 http://git.gnome.org/browse/glib/commit/?id=12060df9f17a48cd4c7fda27a0af70c17c308ad9 This CVE is disputed by upstream, we will not be fixing this issue in stable releases