CVE-2019-20787
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTeeworlds before 0.7.4 has an integer overflow when computing a tilemap size.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceTeeworlds before version 0.7.4 contains an integer overflow vulnerability when calculating tilemap dimensions. This occurs when arithmetic operations during tilemap size computation produce values exceeding the maximum representable value for the data type, causing wraparound and potentially leading to heap buffer overflows or memory corruption when the game allocates or accesses tilemap data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.7.4= 15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Teeworlds installationRun 'teeworlds --version' in a terminal or check the installed package via the system package manager (e.g., 'rpm -q teeworlds' on openSUSE or 'dpkg -l teeworlds' on Debian-based systems)Affected if Teeworlds is installed on the system
-
Determine the installed Teeworlds versionExamine the version string returned by 'teeworlds --version' or the package query command. Note the full version number (e.g., 0.7.3, 0.7.2, 0.6.5)Affected if A version number is returned that is lower than 0.7.4
-
Compare version against the vulnerability thresholdCompare the installed version to the affected range: any version before 0.7.4 is vulnerable. For example, 0.7.3, 0.7.2, 0.7.1, 0.7.0, 0.6.x, and earlier releases are all affectedAffected if The installed version is less than 0.7.4 (e.g., 0.7.3 or earlier)
-
Check the operating system version if using openSUSEIf Teeworlds was installed via the system package manager on openSUSE Leap 15.1, verify the OS version using 'cat /etc/os-release' or 'hostnamectl'Affected if Running openSUSE Leap 15.1 with Teeworlds installed from the distribution packages
A system is affected if it runs any version of Teeworlds earlier than 0.7.4, particularly on openSUSE Leap 15.1 where the packaged version is vulnerable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.7.4
Upgrade to Teeworlds version 0.7.4 or later, which contains the fix for this integer overflow vulnerability.
Teeworlds 0.7.4 or later
- 1. Check current Teeworlds version (typically via --version flag or about dialog in client)
- 2. Download Teeworlds 0.7.4 or later from the official website (www.teeworlds.com) or your distribution's package manager
- 3. Back up any existing game data/configurations if desired
- 4. Install the updated version (0.7.4 or later) using your package manager or by running the downloaded installer
- 5. Restart the Teeworlds client and server components
- 6. Verify the new version is running (should show 0.7.4 or higher)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-20787 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data