Skip to content
Fencer Intel
high 7.5

CVE-2018-17953 json

pam_access does not handle netmask matches correctly

published 7y ago modified 4mo ago also EUVD-2018-9694

cvss
7.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

A incorrect variable in a SUSE specific patch for pam_access rule matching in PAM 1.3.0 in openSUSE Leap 15.0 and SUSE Linux Enterprise 15 could lead to pam_access rules not being applied (fail open).

Patch / fix

  • SUSE pam 1.3.0 before 2018-11-30
  • pam SLE Module for Development Tools 15, SLE Module for Basesystem 15 1.3.0-6.6.1

suse advisories SUSE-SU-2018:3965-1

  • pam openSUSE Tumbleweed 1.5.2-1.1

opensuse advisories openSUSE-SU-2024:11140-1

Is CVE-2018-17953 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-17953 updated cvss 7.5

pam: pam_access.so doesn't properly handle ip addresses and subnets filtering

  • Red Hat Enterprise Linux 5 pam Red Hat Enterprise Linux 6 pam Red Hat Enterprise Linux 7 pam Red Hat Enterprise Linux 8 pam Red Hat Virtualization 4 pam
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • SUSE pam

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.