# CVE-2010-3845: Information disclosure in n/a

> The libapache-authenhook-perl library stores user credentials in plaintext within error logs, allowing attackers with log access to steal sensitive authentication data.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Aug 2017
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-3845, GHSA-7rxx-w8q3-rg72

## What is CVE-2010-3845?

CVE-2010-3845 is a critical vulnerability in n/a, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libapache-authenhook-perl 2.00-04 stores usernames and passwords in plaintext in the vhost error log.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2010-3845?

It affects 1 product.


Products: Apache Authenhook Project Apache Authenhook.

## How do I fix CVE-2010-3845?

Apply the vendor's patch.

## Is CVE-2010-3845 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3845 and fix it if it is affected.

What it is: CVE-2010-3845 is a critical vulnerability in n/a, published on 8 Aug 2017. 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-2010-3845 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-2010-3845/ (Markdown: https://insights.sbomify.com/CVE-2010-3845/index.md)
```

## Sources

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

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