# CVE-2013-7041: Weak cryptography in n/a

> The pam_userdb module uses case-insensitive password comparison, allowing attackers to bypass authentication via brute force attacks.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7041, GHSA-mcg8-3cr3-6hq9, UBUNTU-CVE-2013-7041

## What is CVE-2013-7041?

CVE-2013-7041 is a medium-severity vulnerability in n/a, published on 8 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The pam_userdb module for Pam uses a case-insensitive method to compare hashed passwords, which makes it easier for attackers to guess the password via a brute force attack.

Weakness: CWE-310

## Which versions are affected by CVE-2013-7041?

It affects 1 product.


Products: Cristian Gafton Pam Userdb.

## How do I fix CVE-2013-7041?

Apply the vendor's patch.

## Is CVE-2013-7041 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7041 and fix it if it is affected.

What it is: CVE-2013-7041 is a medium-severity vulnerability in n/a, published on 8 May 2014. 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-2013-7041 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-2013-7041/ (Markdown: https://insights.sbomify.com/CVE-2013-7041/index.md)
```

## Sources

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

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