Skip to content
Fencer Intel
critical 9.8

CVE-2019-20787 json

Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size.

published 6y ago modified 4mo ago also EUVD-2019-11325

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

Summary

Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size.

Patch / fix

  • teeworlds teeworlds 0.7.4
  • teeworlds Ubuntu 20.04 LTS 0.7.2-5

ubuntu advisories UBUNTU-CVE-2019-20787

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • teeworlds openSUSE Tumbleweed 0.7.5-2.9
  • teeworlds Package Hub 15 SP1 0.7.5-bp151.2.6.1
  • teeworlds openSUSE Leap 15.1 0.7.5-lp151.2.6.1

opensuse advisories openSUSE-SU-2024:11427-1openSUSE-SU-2020:0563-1openSUSE-SU-2020:0557-1

Is CVE-2019-20787 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-20787 updated cvss 9.8

teeworlds: there's an integer overflow when computing a tilemap size

  • 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

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

CVSS scores

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

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

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.