LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue could let a logged-in attacker access SUSE Linux Enterprise accounts that administrators intended to disable. The business risk is unauthorized account use, especially on older SLE systems before version 12. The provided sources do not show active exploitation or a named patch level.

Executive priority

Address during legacy Linux remediation work, with higher urgency for internet-reachable or sensitive systems. This is not a confirmed emergency from the supplied evidence, but it affects account disablement controls and can undermine access governance.

Technical view

CVE-2011-3172 is a SUSE Linux Enterprise pam_modules issue where unix2_chkpwd did not check for a valid account. The CVSS 3.0 score is 5.4, with network attack vector and low privileges required. Impacts are limited confidentiality and integrity; availability is not rated impacted.

Likely exposure

Exposure is most likely on SUSE Linux Enterprise releases before 12 using the affected pam_modules behavior. Environments with legacy SLE hosts and disabled local accounts should prioritize verification. The source bundle does not provide exact CPEs or package versions.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not claim active exploitation. The scoring indicates exploitation requires low privileges and no user interaction. Treat this as an access-control weakness in legacy SUSE environments, not confirmed widespread exploitation.

Researcher notes

Evidence is sparse: the bundle identifies SUSE Linux Enterprise before 12, pam_modules, unix2_chkpwd, CWE-304, and CVSS details, but no exact fixed package, affected CPEs, or exploitation evidence. Validate against SUSE Bugzilla and OBS references before making package-level claims.

Mitigation direction

  • Inventory SUSE Linux Enterprise systems and identify releases prior to version 12.
  • Check SUSE guidance and maintenance channels for the corrected pam_modules package.
  • Upgrade affected SLE systems or apply the vendor-provided maintenance update.
  • Review disabled accounts on affected hosts for unexpected access or authentication activity.
  • Use compensating access controls until vendor remediation is confirmed.

Validation and detection

  • Confirm each host's SUSE Linux Enterprise major version and pam_modules package status.
  • Verify disabled accounts cannot authenticate after remediation.
  • Review authentication logs for disabled-account login attempts or successes.
  • Document remaining legacy SLE systems and their remediation owners.
  • Track closure against SUSE advisory or package guidance, not assumed package names.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-304: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2011-3172 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2011-3172Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SUSESUSE Linux EnterpriseunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-304 · source CWE mapping

Missing Critical Step in Authentication

Missing Critical Step in Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.