# CVE-2011-3172: unix2_chkpwd do not check for a valid account

> Attackers can log into disabled accounts due to missing validation in unix2_chkpwd, requiring an OS upgrade to fix.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 8 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jv5w-jhcc-wx4g, SUSE-SU-2018:1760-1, openSUSE-SU-2024:10043-1

## What is CVE-2011-3172?

CVE-2011-3172 is a medium-severity authentication bypass vulnerability in Suse Suse Linux Enterprise Server, published on 8 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in pam_modules of SUSE Linux Enterprise allows attackers to log into accounts that should have been disabled. Affected releases are SUSE Linux Enterprise: versions prior to 12.

Weakness: CWE-264, CWE-304 (Missing Critical Step in Authentication)

## Which versions are affected by CVE-2011-3172?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam-modules` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 11-1.27.3.1 |
| `pam-modules` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 11-1.27.3.1 |
| `pam-modules` | openSUSE:Tumbleweed | All versions | 12.1-27.4 |

Products: Suse Suse Linux Enterprise Server.

## How do I fix CVE-2011-3172?

Upgrade to a fixed version.

## Is CVE-2011-3172 being exploited?

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

## Other vulnerabilities in Suse Suse Linux Enterprise Server

- [CVE-2019-3688](https://insights.sbomify.com/CVE-2019-3688/): squid: /usr/sbin/pinger packaged with wrong permission (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3172 and fix it if it is affected.

What it is: CVE-2011-3172 is a medium-severity authentication bypass vulnerability in Suse Suse Linux Enterprise Server, published on 8 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3172 in the wild and no public exploit code.

Affected product: Suse Suse Linux Enterprise Server. 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-2011-3172/ (Markdown: https://insights.sbomify.com/CVE-2011-3172/index.md)
```

## Sources

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

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