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

> Remote attackers can crash the World in Conflict game client by sending a zero-byte data block to TCP port 48000, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **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-h458-3c33-9wh9

## What is CVE-2008-6713?

CVE-2008-6713 is a medium-severity 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

World in Conflict (WIC) 1.008 and earlier allows remote attackers to cause a denial of service (access violation and crash) via a zero-byte data block to TCP port 48000, which triggers a NULL pointer dereference.

Weakness: CWE-399

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

It affects 1 product.


Products: Massive Entertainment Wic.

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

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

## Is CVE-2008-6713 being exploited?

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

Public exploit code:

- World in Conflict 1.008 - Null Pointer Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6713 is a medium-severity 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-6713 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-6713/ (Markdown: https://insights.sbomify.com/CVE-2008-6713/index.md)
```

## Sources

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

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