CVE-2019-17371
First published: Wed Oct 09 2019(Updated: )
gif2png 2.5.13 has a memory leak in the writefile function.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GIF2PNG Project | =2.5.13 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-17371?
CVE-2019-17371 is classified with a moderate severity level due to its potential memory leak issue.
How does the memory leak in CVE-2019-17371 affect the system?
The memory leak in CVE-2019-17371 can lead to increased memory consumption over time, potentially exhausting system resources.
How do I fix CVE-2019-17371?
To fix CVE-2019-17371, upgrade gif2png to a version that addresses the memory leak issue.
Is CVE-2019-17371 present in earlier versions of gif2png?
Yes, CVE-2019-17371 specifically affects gif2png version 2.5.13 and may impact earlier versions as well.
What should I monitor regarding CVE-2019-17371?
It's crucial to monitor system memory usage and ensure timely updates to the gif2png software to mitigate CVE-2019-17371.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/remedy
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/author
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gif2png project
- canonical/gif2png project
- version/gif2png project/2.5.13