# CVE-2005-4802: Path traversal in n/a

> Local attackers can overwrite files and execute arbitrary code via symlink attacks on temporary files in Flexbackup.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2006
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-4802, DSA-1216-1, GHSA-ff76-wr66-r229

## What is CVE-2005-4802?

CVE-2005-4802 is a medium-severity path traversal vulnerability in n/a, published on 17 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Flexbackup 1.2.1 and earlier allows local users to overwrite files and execute code via a symlink attack on temporary files.  NOTE: the raw source referenced an incorrect candidate number; this is the correct number to use.

## Which versions are affected by CVE-2005-4802?

It affects 1 product.


Products: Flexbackup Flexbackup.

## How do I fix CVE-2005-4802?

Apply the vendor's patch.

## Is CVE-2005-4802 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4802 and fix it if it is affected.

What it is: CVE-2005-4802 is a medium-severity path traversal vulnerability in n/a, published on 17 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4802 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-2005-4802/ (Markdown: https://insights.sbomify.com/CVE-2005-4802/index.md)
```

## Sources

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

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