# CVE-2006-1480: Path traversal in n/a

> Remote attackers can execute arbitrary commands by exploiting a directory traversal vulnerability in the skin2 cookie parameter of WebAlbum.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 29 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-frc3-6h9v-9jxc

## What is CVE-2006-1480?

CVE-2006-1480 is a medium-severity path traversal vulnerability in n/a, published on 29 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in start.php in WebAlbum 2.02 allows remote attackers to include arbitrary files and execute commands by (1) injecting code into local log files via GET commands, then (2) accessing that log via a .. (dot dot) sequence and a trailing null (%00) byte in the skin2 COOKIE parameter.

## Which versions are affected by CVE-2006-1480?

It affects 1 product.


Products: Duda Webalbum.

## How do I fix CVE-2006-1480?

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

## Is CVE-2006-1480 being exploited?

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

Public exploit code:

- WebAlbum 2.02pl - COOKIE[skin2] Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1480 and fix it if it is affected.

What it is: CVE-2006-1480 is a medium-severity path traversal vulnerability in n/a, published on 29 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1480 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-2006-1480/ (Markdown: https://insights.sbomify.com/CVE-2006-1480/index.md)
```

## Sources

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

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