# CVE-2007-4643: Integer overflow in n/a

> Remote attackers can crash the Doomsday game server by sending a malformed chat packet, 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:** 31 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6h87-2fpc-x688

## What is CVE-2007-4643?

CVE-2007-4643 is a medium-severity vulnerability in n/a, published on 31 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer underflow in Doomsday (aka deng) 1.9.0-beta5.1 and earlier allows remote attackers to cause a denial of service (daemon crash) via a PKT_CHAT packet with a data length less than 3, which triggers an erroneous malloc, possibly related to the Sv_HandlePacket function in sv_main.c.

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

## Which versions are affected by CVE-2007-4643?

It affects 1 product.


Products: Doomsday Doomsday.

## How do I fix CVE-2007-4643?

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

## Is CVE-2007-4643 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4642](https://insights.sbomify.com/CVE-2007-4642/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-4644](https://insights.sbomify.com/CVE-2007-4644/): Code injection in n/a (high 7.5)
- [CVE-2006-1618](https://insights.sbomify.com/CVE-2006-1618/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4643 and fix it if it is affected.

What it is: CVE-2007-4643 is a medium-severity vulnerability in n/a, published on 31 Aug 2007. 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-2007-4643 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-2007-4643/ (Markdown: https://insights.sbomify.com/CVE-2007-4643/index.md)
```

## Sources

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

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