# CVE-2007-4226: Path traversal in n/a

> Authenticated administrators can overwrite arbitrary files via path traversal, potentially gaining root access by modifying system files.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5456-4qxw-qgvg

## What is CVE-2007-4226?

CVE-2007-4226 is a high-severity path traversal vulnerability in n/a, published on 8 Aug 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Directory traversal vulnerability in the BlueCat Networks Proteus IPAM appliance 2.0.2.0 (Adonis DNS/DHCP appliance 5.0.2.8) allows remote authenticated administrators, with certain TFTP privileges, to create and overwrite arbitrary files via a .. (dot dot) in a pathname.  NOTE: this can be leveraged for administrative access by overwriting /etc/shadow.

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

It affects 1 product.


Products: Bluecat Networks Adonis.

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

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

## Is CVE-2007-4226 being exploited?

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

Public exploit code:

- BlueCat Networks Adonis 5.0.2.8 - TFTP Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4390](https://insights.sbomify.com/CVE-2007-4390/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4226 is a high-severity path traversal vulnerability in n/a, published on 8 Aug 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4226 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-2007-4226/ (Markdown: https://insights.sbomify.com/CVE-2007-4226/index.md)
```

## Sources

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

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