Skip to content
Fencer Intel
high 7.5

CVE-2019-17178 json

HuffmanTree_makeFromFrequencies in lodepng.c in LodePNG through 2019-09-28, as used in WinPR in FreeRDP and other products, has a memory le…

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

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

Summary

HuffmanTree_makeFromFrequencies in lodepng.c in LodePNG through 2019-09-28, as used in WinPR in FreeRDP and other products, has a memory leak because a supplied realloc pointer (i.e., the first argument to realloc) is also used for a realloc return value.

Patch / fix

  • freerdp2 Debian 12 2.0.0~git20190204.1.2693389a+dfsg1-2

debian advisories DEBIAN-CVE-2019-17178

  • freerdp SLE Workstation Extension 15 SP1 2.0.0~rc4-10.4.1
  • freerdp SLE Workstation Extension 15 2.0.0~rc4-3.10.1
  • freerdp SLED 12 SP4, SLE Workstation Extension 12 SP5, SLE Workstation Extension 12 SP4 +2 more 2.0.0~git.1463131968.4e66df7-12.11.1

suse advisories SUSE-SU-2019:3079-1SUSE-SU-2019:3078-1SUSE-SU-2019:3077-1

  • freerdp openSUSE Leap 15.1 2.0.0~rc4-lp151.5.3.1
  • freerdp openSUSE Leap 15.0 2.0.0~rc4-lp150.10.1

opensuse advisories openSUSE-SU-2019:2608-1openSUSE-SU-2019:2604-1

Is CVE-2019-17178 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

Exploit prediction

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

CVSS scores

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

Classification

Weakness
  • CWE-252 Unchecked Return Value
  • 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.