# SUSE-SU-2018:3311-1: Security update for pam_pkcs11

> An attacker can bypass authentication via replay attacks or execute arbitrary code through a stack-based buffer overflow in the pam_pkcs11 module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Oct 2018

## What is SUSE-SU-2018:3311-1?

SUSE-SU-2018:3311-1 is an authentication bypass vulnerability in pam_pkcs11, published on 23 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for pam_pkcs11 provides the following fixes:

Security issues fixed (bsc#1105012):

- Fixed a logic bug in pampkcs11.c, leading to an authentication replay vulnerability
- Fixed a stack-based buffer overflow in opensshmapper.c
- Make sure memory is properly cleaned before invoking free()

Other changes:

- Add a systemd service file. (bsc#1049219)

## Which versions are affected by SUSE-SU-2018:3311-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam_pkcs11` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 0.6.8-7.5.1 |
| `pam_pkcs11` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 0.6.8-7.5.1 |
| `pam_pkcs11` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 0.6.8-7.5.1 |

## How do I fix SUSE-SU-2018:3311-1?

Apply the vendor's patch.

## Is SUSE-SU-2018:3311-1 being exploited?

There is no known exploitation of SUSE-SU-2018:3311-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2018:3311-1 and fix it if it is affected.

What it is: SUSE-SU-2018:3311-1 is an authentication bypass vulnerability in pam_pkcs11, published on 23 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2018:3311-1 in the wild and no public exploit code.

Affected product: pam_pkcs11. 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/SUSE-SU-2018-3311-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-3311-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2018:3311-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2018-3311-1/
Summaries are generated and may contain mistakes; the official description above is the record.