# CVE-2008-6703: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the game's network packet handling.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p3hc-qpwm-jvqc

## What is CVE-2008-6703?

CVE-2008-6703 is a critical memory corruption vulnerability in n/a, published on 10 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the IPureServer::_Recieve function in S.T.A.L.K.E.R.: Shadow of Chernobyl 1.0006 and earlier allows remote attackers to execute arbitrary code via a compressed 0x39 packet, which is decompressed by the NET_Compressor::Decompress function.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-6703?

It affects 1 product.


Products: Stalker-Game S.t.a.l.k.e.r.\.

## How do I fix CVE-2008-6703?

No fix has been published for CVE-2008-6703 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-6703 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6703 exists.

Public exploit code:

- S.T.A.L.K.E.R Shadow of Chernobyl 1.0006 - Multiple Remote Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6702](https://insights.sbomify.com/CVE-2008-6702/): Denial of service in n/a (medium 5.0)
- [CVE-2008-6704](https://insights.sbomify.com/CVE-2008-6704/): Integer overflow in n/a (medium 5.0)
- [CVE-2008-6705](https://insights.sbomify.com/CVE-2008-6705/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6703 and fix it if it is affected.

What it is: CVE-2008-6703 is a critical memory corruption vulnerability in n/a, published on 10 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6703 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-6703/ (Markdown: https://insights.sbomify.com/CVE-2008-6703/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-6703
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-6703
- OSV: https://osv.dev/vulnerability/CVE-2008-6703

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-6703/
Summaries are generated and may contain mistakes; the official description above is the record.