Skip to content
Fencer Vulns
high 7.5

CVE-2019-20797 json

An issue was discovered in e6y prboom-plus 2.5.1.5.

published 2020-05-17 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-11334

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

Summary

An issue was discovered in e6y prboom-plus 2.5.1.5. There is a buffer overflow in client and server code responsible for handling received UDP packets, as demonstrated by I_SendPacket or I_SendPacketTo in i_network.c.

Patch / fix

  • prboom-plus Debian 11 2:2.5.1.7um+git82-1

debian advisories DEBIAN-CVE-2019-20797

  • prboom-plus openSUSE Tumbleweed 2.6.1um-1.2
  • prboom-plus Package Hub 15 SP1 2.5.1.4-bp151.4.3.1
  • prboom-plus openSUSE Leap 15.1 2.5.1.4-lp151.3.3.1

opensuse advisories openSUSE-SU-2024:11192-1openSUSE-SU-2020:0820-1openSUSE-SU-2020:0807-1

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-20797 updated cvss 7.5

prboom-plus: heap-based buffer overflow in server and client UDP code

  • Red Hat All currently supported Red Hat products
    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

3.09% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • logicaltrust.net https://logicaltrust.net/blog/2019/10/prboom1.html referenced PoC, tagged "exploit" by a source, unverified

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

References

Sources

Fencer Vulns 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.