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

> Local attackers can overwrite arbitrary files with debugging information due to a missing security patch in the Perl package.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** 11 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h95j-w8vr-v949, RHSA-2006:0605

## What is CVE-2006-3813?

CVE-2006-3813 is a low-severity path traversal vulnerability in Redhat Enterprise Linux, published on 11 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A regression error in the Perl package for Red Hat Enterprise Linux 4 omits the patch for CVE-2005-0155, which allows local users to overwrite arbitrary files with debugging information.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl` | Red Hat:enterprise_linux:4::as | All versions | 3:5.8.5-36.RHEL4 |
| `perl-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 3:5.8.5-36.RHEL4 |
| `perl-suidperl` | Red Hat:enterprise_linux:4::as | All versions | 3:5.8.5-36.RHEL4 |
| `perl` | Red Hat:enterprise_linux:4::desktop | All versions | 3:5.8.5-36.RHEL4 |
| `perl-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 3:5.8.5-36.RHEL4 |
| `perl-suidperl` | Red Hat:enterprise_linux:4::desktop | All versions | 3:5.8.5-36.RHEL4 |
| `perl` | Red Hat:enterprise_linux:4::es | All versions | 3:5.8.5-36.RHEL4 |
| `perl-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 3:5.8.5-36.RHEL4 |
| `perl-suidperl` | Red Hat:enterprise_linux:4::es | All versions | 3:5.8.5-36.RHEL4 |
| `perl` | Red Hat:enterprise_linux:4::ws | All versions | 3:5.8.5-36.RHEL4 |
| `perl-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 3:5.8.5-36.RHEL4 |
| `perl-suidperl` | Red Hat:enterprise_linux:4::ws | All versions | 3:5.8.5-36.RHEL4 |

Products: Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2006-3813 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3813 is a low-severity path traversal vulnerability in Redhat Enterprise Linux, published on 11 Aug 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-2006-3813 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-3813/ (Markdown: https://insights.sbomify.com/CVE-2006-3813/index.md)
```

## Sources

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

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