What is the severity of CVE-2016-2052?

The severity of CVE-2016-2052 is classified as high due to the potential for denial of service and other impacts from exploited vulnerabilities.

How do I fix CVE-2016-2052?

To remediate CVE-2016-2052, update HarfBuzz to version 1.0.6 or later, and update Google Chrome to version 48.0.2564.82 or later.

What type of vulnerabilities are associated with CVE-2016-2052?

CVE-2016-2052 is associated with multiple unspecified vulnerabilities that could lead to denial of service via crafted data.

Which versions of HarfBuzz are affected by CVE-2016-2052?

HarfBuzz versions before 1.0.6 are affected by CVE-2016-2052.

Which versions of Google Chrome are impacted by CVE-2016-2052?

Google Chrome versions before 48.0.2564.82 are impacted by CVE-2016-2052.

Vulnerability/
CVE-2016-2052

high

7.6

25/1/2016

5/8/2024

CVE-2016-2052

First published: Mon Jan 25 2016(Updated: )

Multiple unspecified vulnerabilities in HarfBuzz before 1.0.6, as used in Google Chrome before 48.0.2564.82, allow attackers to cause a denial of service or possibly have other impact via crafted data, as demonstrated by a buffer over-read resulting from an inverted length check in hb-ot-font.cc, a different issue than CVE-2015-8947.

Credit: cve-coordination@google.com

Affected Software	Affected Version	How to fix
HarfBuzz	<=1.0.5
Google Chrome	<=47.0.2526.106

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-2052?
The severity of CVE-2016-2052 is classified as high due to the potential for denial of service and other impacts from exploited vulnerabilities.
How do I fix CVE-2016-2052?
To remediate CVE-2016-2052, update HarfBuzz to version 1.0.6 or later, and update Google Chrome to version 48.0.2564.82 or later.
What type of vulnerabilities are associated with CVE-2016-2052?
CVE-2016-2052 is associated with multiple unspecified vulnerabilities that could lead to denial of service via crafted data.
Which versions of HarfBuzz are affected by CVE-2016-2052?
HarfBuzz versions before 1.0.6 are affected by CVE-2016-2052.
Which versions of Google Chrome are impacted by CVE-2016-2052?
Google Chrome versions before 48.0.2564.82 are impacted by CVE-2016-2052.

agent/references
agent/type
agent/softwarecombine
agent/author
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/harfbuzz project
canonical/harfbuzz
version/harfbuzz/1.0.5
vendor/google
canonical/google chrome
version/google chrome/47.0.2526.106

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2016-2052?
The severity of CVE-2016-2052 is classified as high due to the potential for denial of service and other impacts from exploited vulnerabilities.
How do I fix CVE-2016-2052?
To remediate CVE-2016-2052, update HarfBuzz to version 1.0.6 or later, and update Google Chrome to version 48.0.2564.82 or later.
What type of vulnerabilities are associated with CVE-2016-2052?
CVE-2016-2052 is associated with multiple unspecified vulnerabilities that could lead to denial of service via crafted data.
Which versions of HarfBuzz are affected by CVE-2016-2052?
HarfBuzz versions before 1.0.6 are affected by CVE-2016-2052.
Which versions of Google Chrome are impacted by CVE-2016-2052?
Google Chrome versions before 48.0.2564.82 are impacted by CVE-2016-2052.