CVE-2016-1709 Memory corruption in n/a
Remote attackers can cause denial of service or potential code execution via crafted SFNT fonts due to a heap buffer overflow in the sfntly library used by Chrome.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2016-1709?
CVE-2016-1709 is a high-severity memory corruption vulnerability in Google Chrome, published on 23 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Heap-based buffer overflow in the ByteArray::Get method in data/byte_array.cc in Google sfntly before 2016-06-10, as used in Google Chrome before 52.0.2743.82, allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted SFNT font.
Weakness: CWE-119
Which versions are affected by CVE-2016-1709?
It affects 2 products.
Products include Google Chrome, Google Sfntly.
How do I fix CVE-2016-1709?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2016-1709 being exploited?
There is no known exploitation of CVE-2016-1709 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-frpp-5h48-9qqg, UBUNTU-CVE-2016-1709.