CVE-2017-6363 Memory corruption in n/a
A heap-based buffer over-read in the GD Graphics Library allows attackers to cause denial of service or disclose sensitive memory information.
- 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-2017-6363?
CVE-2017-6363 is a high-severity memory corruption vulnerability in n/a, published on 27 Feb 2020. 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
In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for development and testing purposes.'
Weakness: CWE-125
Which versions are affected by CVE-2017-6363?
It affects 1 product.
Products include Libgd Libgd.
How do I fix CVE-2017-6363?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-6363 being exploited?
There is no known exploitation of CVE-2017-6363 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as ALPINE-CVE-2017-6363, DEBIAN-CVE-2017-6363, GHSA-pfv9-ff57-j64p, UBUNTU-CVE-2017-6363.