# CVE-2007-4379: Denial of service in n/a

> Remote attackers can crash the Babo Violent 2 game client by sending malformed UDP packets or invalid data IDs.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 16 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3273-p572-3fr8

## What is CVE-2007-4379?

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

### Official description

Babo Violent 2 2.08.00 and earlier allows remote attackers to cause a denial of service (application crash) via (1) a value greater than 0x27 for the (a) 0xca, (b) 0xcb, (c) 0xcc, (d) 0xce, (e) 0xcf, or (f) 0xd0 data ID; (2) a nonexistent map name; or (3) a UDP packet that specifies a large data size.

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

It affects 1 product.


Products: Rndlabs Babo Violent.

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

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

## Is CVE-2007-4379 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4373](https://insights.sbomify.com/CVE-2007-4373/): Auth bypass in n/a (medium 6.8)
- [CVE-2007-4378](https://insights.sbomify.com/CVE-2007-4378/): Other in n/a (medium 6.8)
- [CVE-2007-4374](https://insights.sbomify.com/CVE-2007-4374/): Missing authorization in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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