Analyst readout for executives and security teams
Plain-English summary
This is an old denial-of-service flaw in Ground Control II: Operation Exodus. A hostile remote server could send an oversized packet that makes vulnerable clients or servers crash. The issue affects availability, not data theft or system compromise, based on the provided sources.
Executive priority
Low business urgency for most organizations, unless this legacy game is still operated in a public or business-critical context. Treat it as a legacy availability risk and prioritize removal, isolation, or vendor-guidance review over emergency response.
Technical view
Ground Control II: Operation Exodus 1.0.0.7 and earlier mishandles a large packet. The resulting “Message too long” socket error is treated as critical, causing a client or server crash. No CVSS, CWE, patch details, or complete vendor/product metadata are provided in the bundle.
Likely exposure
Exposure is likely limited to legacy installations of Ground Control II: Operation Exodus 1.0.0.7 or earlier, especially clients connecting to remote servers or hosted game servers reachable by other players. Most modern enterprise environments are unlikely to run this software.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Public advisory references exist from 2004, but the supplied data supports only denial-of-service impact and does not establish current exploitation.
Researcher notes
The source bundle is sparse: affected metadata is incomplete, severity is unknown, and no authoritative remediation is included. Analysis should stay constrained to availability impact in Ground Control II: Operation Exodus 1.0.0.7 and earlier.
Mitigation direction
- Identify any Ground Control II installations or hosted servers.
- Check vendor or community guidance for fixed versions or workarounds.
- Avoid connecting vulnerable clients to untrusted remote servers.
- Restrict access to any hosted game servers where feasible.
- Retire unsupported installations if no maintained fix exists.
Validation and detection
- Confirm whether Ground Control II is present in asset records.
- Verify installed versions are later than 1.0.0.7, if still used.
- Review network exposure for any hosted game server components.
- Check crash reports for unexplained socket error failures.
- Document unsupported legacy software risk decisions.
Public sources used
Based on public source material and reviewed before publication.
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-2004-1751 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- 20040826 Broadcast forced exit in Ground Control II 1.0.0.7CVE reference · mailing-list, x_refsource_BUGTRAQ
- http://aluigi.altervista.org/adv/gc2boom-adv.txtCVE reference · x_refsource_MISC
- ground-control-dos(17130)CVE reference · vdb-entry, x_refsource_XF
- 11058CVE reference · vdb-entry, x_refsource_BID
- 1011075CVE reference · vdb-entry, x_refsource_SECTRACK
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.