Skip to content
Fencer Intel
high 8.8

CVE-2018-17076 json

GPP through 2.25 will try to use more memory space than is available on the stack, leading to a segmentation fault or possibly unspecified…

published 8y ago modified 4mo ago also EUVD-2018-8856

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

GPP through 2.25 will try to use more memory space than is available on the stack, leading to a segmentation fault or possibly unspecified other impact via a crafted file.

Patch / fix

  • gpp Debian 14, Debian 13, Debian 12 2.26-1

debian advisories DEBIAN-CVE-2018-17076

  • gpp openSUSE Tumbleweed 2.28-1.1

opensuse advisories openSUSE-SU-2024:13313-1

Is CVE-2018-17076 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

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

Exploits and checks

  • github.com https://github.com/logological/gpp/issues/26 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.