# CVE-2007-4100: Security feature bypass in n/a

> Remote attackers can bypass IP blocklists in MLDonkey by exploiting a race condition during startup, allowing unauthorized network access.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vmg6-hwvc-96fg

## What is CVE-2007-4100?

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

### Official description

MLDonkey before 2.9.0 does not load certain code from $MLDONKEY/web_infos/ before the network modules become active, which allows remote attackers to bypass the IP blocklist.

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

It affects 1 product.


Products: Mldonkey Mldonkey.

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

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

## Is CVE-2007-4100 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0753](https://insights.sbomify.com/CVE-2009-0753/): Path traversal in n/a (medium 5.0)
- [CVE-2003-1164](https://insights.sbomify.com/CVE-2003-1164/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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