Skip to content
Fencer Intel
medium 6.5

CVE-2019-17371 json

gif2png 2.5.13 has a memory leak in the writefile function.

published 7y ago modified 4mo ago also EUVD-2019-7778

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

gif2png 2.5.13 has a memory leak in the writefile function.

Patch / fix

Is CVE-2019-17371 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-17371 updated cvss 6.5

libpng: memory leaks in png_malloc_warn and png_create_info_struct

  • Red Hat Enterprise Linux 5 libpng Red Hat Enterprise Linux 6 libpng Red Hat Enterprise Linux 7 libpng, libpng12 Red Hat Enterprise Linux 8 libpng, libpng12, libpng15, mingw-libpng, mingw32-libpng, mingw64-libpng
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/glennrp/libpng/issues/307#issuecomment-544779431 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/glennrp/libpng/issues/307 referenced PoC, tagged "exploit" by a source, unverified
  • gitlab.com https://gitlab.com/esr/gif2png/issues/8 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.