CVE-2016-2052
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of service disruption.
- Exploit odds
- 1.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.0% in the next 30 days (EPSS).
- Severity: 7.6 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.0% · EPSS, next 30 days
- Record status
- Modified
Affected
- Harfbuzz Project Harfbuzz ≤ 1.0.5
- Google Chrome ≤ 47.0.2526.106
Attack profile CVSS 3.0 · 7.6
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-2052.md and follow it. Check whether this project is affected by CVE-2016-2052. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/behdad/harfbuzz/commit/63ef0b41dc48d6112d1918c1b1de9de8ea90adb5
- https://github.com/behdad/harfbuzz/commit/63ef0b41dc48d6112d1918c1b1de9de8ea90adb5
References
- http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html
- http://lists.opensuse.org/opensuse-updates/2016-08/msg00070.html
- http://rhn.redhat.com/errata/RHSA-2016-0072.html
- http://www.securityfocus.com/bid/81812
- http://www.securitytracker.com/id/1034801
- http://www.ubuntu.com/usn/USN-2877-1
- http://www.ubuntu.com/usn/USN-3067-1
- https://code.google.com/p/chromium/issues/detail?id=544270
- https://code.google.com/p/chromium/issues/detail?id=579625
- https://github.com/behdad/harfbuzz/commit/63ef0b41dc48d6112d1918c1b1de9de8ea90adb5
- https://github.com/behdad/harfbuzz/issues/139#issuecomment-148289957
- https://security.gentoo.org/glsa/201701-76
- http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html
- http://lists.opensuse.org/opensuse-updates/2016-08/msg00070.html
- http://rhn.redhat.com/errata/RHSA-2016-0072.html
- http://www.securityfocus.com/bid/81812
- http://www.securitytracker.com/id/1034801
- http://www.ubuntu.com/usn/USN-2877-1
- http://www.ubuntu.com/usn/USN-3067-1
- https://code.google.com/p/chromium/issues/detail?id=544270
- https://code.google.com/p/chromium/issues/detail?id=579625
- https://github.com/behdad/harfbuzz/commit/63ef0b41dc48d6112d1918c1b1de9de8ea90adb5
- https://github.com/behdad/harfbuzz/issues/139#issuecomment-148289957
- https://security.gentoo.org/glsa/201701-76