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

> Attackers can bypass authentication via smartcard replay or trigger buffer overflows in the pam_pkcs11 module, potentially leading to privilege escalation or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Sep 2018

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

SUSE-SU-2018:2843-1 is an authentication bypass vulnerability in pam_pkcs11, published on 24 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

This update for pam_pkcs11 fixes the following security issues:

- It was possible to replay an authentication by using a specially prepared smartcard or token (bsc#1105012)
- Prevent buffer overflow if a user has a home directory with a length of more than 512 bytes (bsc#1105012)
- Memory not cleaned properly before free() (bsc#1105012)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam_pkcs11` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 0.6.0-141.3.1 |
| `pam_pkcs11` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 0.6.0-141.3.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2018:2843-1 is an authentication bypass vulnerability in pam_pkcs11, published on 24 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of SUSE-SU-2018:2843-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-2843-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-2843-1/index.md)
```

## Sources

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

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