UFO: Alien Invasion versions up to and including 2.2.1 contain a buffer overflow vulnerability in its built-in IRC client component. When the client connects to an IRC server and receives a crafted numeric reply (specifically a 001 message), the application fails to properly validate the length of the response string. This results in a stack-based buffer overflow, which may corrupt control flow structures and allow arbitrary code execution. The vulnerability is triggered during automatic IRC connection handling and does not require user interaction beyond launching the game.
Security readout for executives and security teams
Plain-English summary
This affects an old UFO: Alien Invasion game client. A malicious IRC server response can overflow memory in the built-in IRC client and potentially run code on the player’s machine. Business exposure is likely limited unless the game exists on managed endpoints, labs, or legacy images.
Executive priority
Treat as urgent only where the game is actually present. The technical impact is severe, but enterprise exposure is probably narrow and should be confirmed by inventory before broad response effort.
Technical view
The issue is a stack-based buffer overflow in the UFO: Alien Invasion IRC client when processing an overly long IRC 001 numeric reply. The bundle describes network, unauthenticated, no-user-interaction exploitation after the game connects to IRC. Public exploit references exist, but KEV is false.
Likely exposure
Most enterprises will have low prevalence, but any endpoint running UFO: Alien Invasion 2.2.1 or older may be exposed when its built-in IRC client connects to an IRC server.
Exploitation context
The source bundle cites public exploit references for Windows and OS X. It does not cite CISA KEV listing or active in-the-wild exploitation, so active exploitation should not be assumed.
Researcher notes
Affected-version evidence is partly inconsistent: the narrative says versions through 2.2.1, while the affected metadata is sparse. Base triage on installed version, IRC-client reachability, and the vendor 2.3.1 release reference.
Mitigation direction
Inventory endpoints for UFO: Alien Invasion installations at or below 2.2.1.
Upgrade vulnerable installations to 2.3.1 or later, based on vendor release evidence.
Remove the game from managed or sensitive systems where it is not required.
Until updated, avoid connecting the built-in IRC client to untrusted IRC servers.
Check current vendor guidance if a supported maintained build is required.
Validation and detection
Confirm installed UFO: Alien Invasion version on relevant endpoints.
Identify whether the built-in IRC client is enabled or used.
Verify upgraded systems report version 2.3.1 or later.
Review software inventory for legacy Windows or OS X game installations.
Do not validate by running public exploit code in production.
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.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.