CVE-2019-17371: gif2png 2.5.13 has a memory leak in the writefile function.
CVE-2019-17371 is a medium-severity flaw (CVSS 6.5) affecting gif2png. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
gif2png 2.5.13 has a memory leak in the writefile function.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 1.7% (top 22%) |
| CISA exploited list | No |
| Weakness | CWE-401 |
| Published | 2019-10-09 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2019-17371?
gif2png: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2019-17371 being exploited?
CVE-2019-17371 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2019-17371 affect?
CVE-2019-17371 affects gif2png. Severity is medium (CVSS 6.5). gif2png 2.5.13 has a memory leak in the writefile function.
How urgent is CVE-2019-17371?
Priority 47/100. Public exploit reference