VYPR
Unrated severityNVD Advisory· Published Feb 20, 2018· Updated Aug 5, 2024

CVE-2017-6193

CVE-2017-6193

Description

Buffer overflow in APNGDis 2.8 and earlier allows remote attackers to cause a denial of service and possibly execute arbitrary code via a crafted image containing a malformed image size descriptor in the IHDR chunk.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A heap buffer overflow in APNGDis 2.8 allows remote code execution via a crafted PNG with malformed IHDR width/height.

Vulnerability

APNGDis 2.8 and earlier contains a heap buffer overflow vulnerability in the compose_frame function. When processing a crafted APNG file with malformed width and height values in the IHDR chunk, the application allocates a buffer based on these values and then performs a memcpy with a size that exceeds the allocated buffer, leading to a heap overflow. The affected versions include all releases up to 2.8 [1].

Exploitation

An attacker can exploit this by providing a specially crafted PNG image with overly large width and height dimensions (e.g., 0x0F000000) in the IHDR chunk. When the application opens the file, it attempts to process the image, triggering the overflow in compose_frame during memory copy operations. No special privileges are required; the attack vector is through file opening. Remote exploitation is possible if the victim opens the malicious file [1].

Impact

Successful exploitation can lead to a denial of service or arbitrary code execution. The heap overflow can corrupt memory structures, potentially allowing an attacker to control execution flow. The CVSS score indicates high severity.

Mitigation

As of this writing, no official patch has been released for APNGDis 2.8. The software appears to be unmaintained. Users should avoid opening untrusted PNG files with APNGDis. No workaround is available.

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.