# CVE-2005-2963: Auth bypass in n/a

> Remote authenticated users can bypass security restrictions in Apache when using the mod_auth_shadow module with specific group directives.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 13 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-844-1, GHSA-92pr-mcw9-qp7f

## What is CVE-2005-2963?

CVE-2005-2963 is a high-severity authentication bypass vulnerability in n/a, published on 13 Oct 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The mod_auth_shadow module 1.0 through 1.5 and 2.0 for Apache with AuthShadow enabled uses shadow authentication for all locations that use the require group directive, even when other authentication mechanisms are specified, which might allow remote authenticated users to bypass security restrictions.

## Which versions are affected by CVE-2005-2963?

It affects 1 product.


Products: Mod Auth Shadow Mod Auth Shadow.

## How do I fix CVE-2005-2963?

Apply the vendor's patch.

## Is CVE-2005-2963 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0041](https://insights.sbomify.com/CVE-2004-0041/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2963 and fix it if it is affected.

What it is: CVE-2005-2963 is a high-severity authentication bypass vulnerability in n/a, published on 13 Oct 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2963 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-2005-2963/ (Markdown: https://insights.sbomify.com/CVE-2005-2963/index.md)
```

## Sources

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

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