# CVE-2007-4373: Auth bypass in n/a

> Remote attackers can bypass authentication in Babo Violent 2 server by reconnecting after a connection closes, gaining unauthorized access.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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-wrqx-442q-74r6

## What is CVE-2007-4373?

CVE-2007-4373 is a medium-severity authentication bypass 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

The server in Babo Violent 2 2.08.00 and earlier does not properly implement password protection, which might allow remote attackers to bypass authentication by reconnecting after a connection closes.

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

It affects 1 product.


Products: Rndlabs Babo Violent.

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

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

## Is CVE-2007-4373 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4378](https://insights.sbomify.com/CVE-2007-4378/): Other in n/a (medium 6.8)
- [CVE-2007-4379](https://insights.sbomify.com/CVE-2007-4379/): Denial of service in n/a (medium 4.3)
- [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-4373 and fix it if it is affected.

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

## Sources

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

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