CVE-2011-0064: Null Pointer Dereference

Published Feb 18, 2011
·
Updated

It was discovered that pango did not check for memory reallocation failures in hbbufferensure() function. This could trigger a NULL pointer dereference in hbbufferaddglyph(), where possibly untrusted input is used as an index used for accessing members of the incorrectly reallocated array, resulting in the use of NULL address as the base array address. This can result in application crash or, possibly, code execution.

It was demonstrated that it's possible to trigger this flaw in Firefox via a specially crafted web page.

Mozilla bug report (currently not public): https://bugzilla.mozilla.org/showbug.cgi?id=606997

Fix in the harfbuzz git: http://cgit.freedesktop.org/harfbuzz/commit/?id=a6a79df5fe2e

Acknowledgements:

Red Hat would like to thank Mozilla Security Team for reporting this issue.

Other sources

The hbbufferensure function in hb-buffer.c in HarfBuzz, as used in Pango 1.28.3, Firefox, and other products, does not verify that memory reallocations succeed, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) or possibly execute arbitrary code via crafted OpenType font data that triggers use of an incorrect index.

MITRE

Affected Software

2 affected components
gnome Pango=1.28.3
Mozilla Firefox

Event History

Feb 18, 2011
Data Sourced
via Red Hat·12:43 PM
DescriptionSeverityAffected Software
Mar 7, 2011
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-0064?

CVE-2011-0064 is classified as a moderate severity vulnerability due to the potential for a NULL pointer dereference.

2

How do I fix CVE-2011-0064?

To fix CVE-2011-0064, update your Pango library to a version that contains the patch addressing memory reallocation failure.

3

Which software is affected by CVE-2011-0064?

CVE-2011-0064 affects versions of Mozilla Firefox and Pango version 1.28.3.

4

What causes the vulnerability identified as CVE-2011-0064?

The CVE-2011-0064 vulnerability is caused by the lack of memory reallocation failure checks in the hb_buffer_ensure() function.

5

Can untrusted input trigger the vulnerability in CVE-2011-0064?

Yes, CVE-2011-0064 can be triggered by possibly untrusted input being used as an index in a dereferenced array.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203