LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000224: Godot Engine version All versions prior to 2.1.5, all 3.0 versions prior to 3.0.6.

Godot Engine version All versions prior to 2.1.5, all 3.0 versions prior to 3.0.6. contains a Signed/unsigned comparison, wrong buffer size chackes, integer overflow, missing padding initialization vulnerability in (De)Serialization functions (core/io/marshalls.cpp) that can result in DoS (packet of death), possible leak of uninitialized memory. This attack appear to be exploitable via A malformed packet is received over the network by a Godot application that uses built-in serialization (e.g. game server, or game client). Could be triggered by multiplayer opponent. This vulnerability appears to have been fixed in 2.1.5, 3.0.6, master branch after commit feaf03421dda0213382b51aff07bd5a96b29487b.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects older Godot Engine releases and can let a malformed network packet crash a Godot application using built-in serialization. Sources also describe possible leakage of uninitialized memory. Business urgency depends on whether vulnerable Godot multiplayer servers or clients are still deployed.

Executive priority

Treat this as a targeted remediation item for legacy Godot deployments, not a broad enterprise emergency. Prioritize internet-facing or opponent-facing multiplayer systems because the reported impact is denial of service and possible memory disclosure from network input.

Technical view

The flaw is in Godot core/io/marshalls.cpp serialization and deserialization logic, involving signed/unsigned comparisons, incorrect buffer-size checks, integer overflow, and missing padding initialization. It affects versions before 2.1.5 and 3.0.x before 3.0.6, with fixes referenced in those releases and the master branch after commit feaf03421dda0213382b51aff07bd5a96b29487b.

Likely exposure

Exposure is most likely in Godot applications built with vulnerable engine versions that receive network data using built-in serialization, especially multiplayer game servers or clients. The provided sources do not identify affected CPEs or downstream applications.

Exploitation context

The source bundle says exploitation requires a malformed packet received over the network by a Godot application using built-in serialization, potentially from a multiplayer opponent. There is no KEV listing and no cited evidence of active exploitation.

Researcher notes

Evidence is specific about vulnerable versions, impacted serialization code, attack precondition, and fixed releases. It does not provide CVSS, CPE mappings, exploit maturity, or confirmed real-world exploitation. Avoid expanding scope beyond Godot applications that use the vulnerable built-in serialization path.

Mitigation direction

  • Upgrade Godot 2.x deployments to 2.1.5 or later.
  • Upgrade Godot 3.0 deployments to 3.0.6 or later.
  • Check Godot release guidance for any branch-specific remediation details.
  • Rebuild and redeploy affected applications after upgrading the engine.
  • Prioritize network-exposed multiplayer services using built-in serialization.

Validation and detection

  • Inventory deployed applications and record their Godot engine versions.
  • Confirm no production build uses Godot before 2.1.5 or 3.0.6.
  • Review whether built-in serialization handles untrusted network input.
  • Check multiplayer servers and clients for unexpected crash patterns.
  • Verify upgraded builds are deployed, not only source repositories.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-1000224 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.