# CVE-2008-3597: Null dereference in n/a

> Remote attackers can crash the Skulltag game server by sending a specific packet when the player is not in the game.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fpxv-5mjh-r2rq

## What is CVE-2008-3597?

CVE-2008-3597 is a high-severity vulnerability in n/a, published on 12 Aug 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Skulltag before 0.97d2-RC6 allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) by sending a "command 29" packet when the player is not in the game.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Skulltag Skulltag.

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

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

## Is CVE-2008-3597 being exploited?

There is no known exploitation of CVE-2008-3597 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3597 is a high-severity vulnerability in n/a, published on 12 Aug 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3597 in the wild and no public exploit code.

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-3597/ (Markdown: https://insights.sbomify.com/CVE-2008-3597/index.md)
```

## Sources

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

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