# CVE-2006-6071: Auth bypass in n/a

> Remote attackers can read arbitrary wiki content by exploiting a flaw in failed login handling under specific Apache configurations.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rj78-gp9g-5m7c

## What is CVE-2006-6071?

CVE-2006-6071 is a critical authentication bypass vulnerability in n/a, published on 2 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TWiki 4.0.5 and earlier, when running under Apache 1.3 using ApacheLogin with sessions and "ErrorDocument 401" redirects to a valid wiki topic, does not properly handle failed login attempts, which allows remote attackers to read arbitrary content by cancelling out of a failed authentication with a valid username and invalid password.

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

It affects 1 product.


Products: Twiki Twiki.

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

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

## Is CVE-2006-6071 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5305](https://insights.sbomify.com/CVE-2008-5305/): Code injection in n/a (critical 10.0)
- [CVE-2013-1751](https://insights.sbomify.com/CVE-2013-1751/): Command injection in n/a (critical 9.8)
- [CVE-2005-3056](https://insights.sbomify.com/CVE-2005-3056/): Command injection in n/a (critical 9.8)
- [CVE-2014-7236](https://insights.sbomify.com/CVE-2014-7236/): Code injection in n/a (critical 9.1)
- [CVE-2006-3819](https://insights.sbomify.com/CVE-2006-3819/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6071 is a critical authentication bypass vulnerability in n/a, published on 2 Dec 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-6071 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-6071/ (Markdown: https://insights.sbomify.com/CVE-2006-6071/index.md)
```

## Sources

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

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