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

> Remote attackers can read arbitrary files via directory traversal in the ze_langue_02 cookie of A.l-Pifou.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/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:** 21 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5857-hf4f-hj7c

## What is CVE-2006-4914?

CVE-2006-4914 is a low-severity path traversal vulnerability in n/a, published on 21 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in A.l-Pifou 1.8p2 allows remote attackers to read arbitrary files via ".." sequences in the ze_langue_02 cookie, as demonstrated by using the choix_lng parameter to choix_langue.php to indirectly set the cookie, then accessing livre_dor.php to trigger the inclusion from inc/change_lang_ck.php, possibly related to livre_livre.php.  NOTE: the livre_livre.php relationship has been reported by some third party sources.

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

It affects 1 product.


Products: A.l-Pifou A.l-Pifou.

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

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

## Is CVE-2006-4914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4914 is a low-severity path traversal vulnerability in n/a, published on 21 Sep 2006. 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-2006-4914 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-2006-4914/ (Markdown: https://insights.sbomify.com/CVE-2006-4914/index.md)
```

## Sources

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

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