dbcve.org
Call Of Duty 4Application · Activision

CVE-2008-2106

MEDIUM · 6.8 CVSS v2.0 Published 2008-05-07
Fix available
A fix is available. Upgrade to after 1.5 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Call of Duty 4 (CoD4) 1.5 and earlier allows remote authenticated users to cause a denial of service (crash) via a type 7 stats packet, which triggers a memcpy with a negative value.

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 confidence

Call of Duty 4 versions 1.5 and earlier contain a denial of service vulnerability where remote authenticated users can send a specially crafted 'type 7' stats packet. This packet triggers a memcpy call with a negative value as the size parameter, causing the game server to crash.

MitigationUpgrade CoD4 server to a version beyond 1.5. If upgrading is not feasible, implement network-level filtering to detect and block malformed stats packets before they reach the game server.

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
Call Of Duty 4Application
Affected:<= 1.5

CVSS 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
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/C:N/I:N/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CoD4 server version
    Locate the server executable or version configuration file and determine the installed version number. Common locations include the server binary or a version manifest file in the game server directory.
    Affected if The installed version is 1.5 or any version lower than 1.5
  2. Verify server is network-accessible
    Confirm the game server has an open port (default 28960) accepting remote connections. Check firewall rules and network configuration to ensure the server is reachable from external sources.
    Affected if The server is accessible from remote networks, allowing external users to send packets to it
  3. Confirm stats functionality is enabled
    Check the server configuration files for settings related to stats, remote query, or RCON that enable processing of stats packets from remote clients.
    Affected if Stats processing or remote query functionality is enabled, allowing remote authenticated users to send type 7 stats packets to the server

You are affected if your CoD4 server version is 1.5 or earlier AND the server is network-accessible with stats/remote query functionality enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 1.5
Interim mitigation

Upgrade CoD4 server to a version beyond 1.5. If upgrading is not feasible, implement network-level filtering to detect and block malformed stats packets before they reach the game server.

Fix this in Call Of Duty 4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-2106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-2106 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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