CVE-2008-6704
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 · uneditedInteger overflow in the NET_Compressor::Decompress function in S.T.A.L.K.E.R.: Shadow of Chernobyl 1.0006 and earlier allows remote attackers to cause a denial of service (server crash) via a crafted packet with a 0xc1 value that contains no compressed data, which triggers a copy of a large amount of memory.
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 · high confidenceInteger overflow in the NET_Compressor::Decompress function in S.T.A.L.K.E.R.: Shadow of Chernobyl v1.0006 and earlier allows remote attackers to crash the game server via a crafted packet with a 0xc1 value containing no compressed data, which triggers an uncontrolled memory copy operation.
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<= 1.0006CVSS 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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Confirm S.T.A.L.K.E.R. server is runningCheck running processes for stalker_game.exe, xrEngine.exe, or similar S.T.A.L.K.E.R. server processes using Task Manager or tasklist commandAffected if The game server process is actively running and listening for network connections
-
Identify installed game versionRight-click on the game executable (stalker.exe or xrEngine.exe), select Properties, and check the Version tab for the file version, or check the version in the game's readme or startup log fileAffected if The installed version is 1.0006 or earlier, or if no version number is displayed and the game was installed prior to any patches
-
Verify network listener is activeUse netstat -an or a network port scanner to check if the game server is listening on UDP/TCP ports (S.T.A.L.K.E.R. typically uses ports 2700-2705 for multiplayer)Affected if The server is bound to network ports and accepting external connections, making it reachable for crafted packet attacks
-
Check for crash logs or anomaly recordsExamine the game logs directory (typically in the game root or logs folder) for recent crash dumps, error messages, or network-related warnings mentioning NET_Compressor or decompression failuresAffected if Recent crash logs or error entries reference decompression issues, memory copy failures, or packet processing errors
You are affected if the S.T.A.L.K.E.R. server is running version 1.0006 or earlier and is exposed to network traffic, as the integer overflow in NET_Compressor::Decompress can be triggered by a specially crafted 0xc1 packet.
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.
From vendor dataDeploy network-level filtering to reject malformed 0xc1 packets, or implement bounds checking in the decompression routine to validate packet size fields before memory allocation/copy operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-6704 — 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-2008-6704 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