# CVE-2006-3458: Zope allows local users to read arbitrary files

> Attackers can read arbitrary files by exploiting the raw command in reStructuredText processing, requiring untrusted user access.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1113, GHSA-jcjp-qqpq-pc54

## What is CVE-2006-3458?

CVE-2006-3458 is a low-severity path traversal vulnerability in n/a, published on 7 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zope 2.7.0 to 2.7.8, 2.8.0 to 2.8.7, and 2.9.0 to 2.9.3 (Zope2) does not disable the "raw" command when providing untrusted users with restructured text (reStructuredText) functionality from docutils, which allows local users to read arbitrary files.

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

6 open source packages ship an affected version, including Zope2 and zope2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Zope2` | PyPI | From 2.7.0 | 2.7.8 |
| `Zope2` | PyPI | From 2.8.0 | 2.8.7 |
| `Zope2` | PyPI | From 2.9.0 | 2.9.3 |
| `zope2` | PyPI | From 2.7.0 | 2.7.8 |
| `zope2` | PyPI | From 2.8.0 | 2.8.7 |
| `zope2` | PyPI | From 2.9.0 | 2.9.3 |

Products: Zope Zope.

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

Upgrade Zope2 to a fixed version for your release line: 2.7.8, 2.8.7 or 2.9.3.

## Is CVE-2006-3458 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0062](https://insights.sbomify.com/CVE-2000-0062/): Zope DTML implementation Improper Authentication (critical 10.0)
- [CVE-2021-32674](https://insights.sbomify.com/CVE-2021-32674/): Remote Code Execution via traversal in TAL expressions (high 8.8)
- [CVE-2000-1211](https://insights.sbomify.com/CVE-2000-1211/): Zope does not properly perform security registration for legacy names (high 7.5)
- [CVE-2002-0170](https://insights.sbomify.com/CVE-2002-0170/): Zope does not properly verify the access for objects with proxy roles (high 7.5)
- [CVE-2002-0688](https://insights.sbomify.com/CVE-2002-0688/): ZCatalog plug-in for Zope allows anonymous users to bypass access restrictions (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3458 is a low-severity path traversal vulnerability in n/a, published on 7 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3458 in the wild and no public exploit code.

Affected packages and fixed versions:
- Zope2 (PyPI): affected from 2.7.0; fixed in 2.7.8
- Zope2 (PyPI): affected from 2.8.0; fixed in 2.8.7
- Zope2 (PyPI): affected from 2.9.0; fixed in 2.9.3
- zope2 (PyPI): affected from 2.7.0; fixed in 2.7.8
- zope2 (PyPI): affected from 2.8.0; fixed in 2.8.7
- zope2 (PyPI): affected from 2.9.0; fixed in 2.9.3

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-3458/ (Markdown: https://insights.sbomify.com/CVE-2006-3458/index.md)
```

## Sources

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

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