# CVE-2023-6258: Pkcs11-provider: side-channel proofing pkcs#1 1.5 paths


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** DEBIAN-CVE-2023-6258, GHSA-phf3-25c6-93hv

## What is CVE-2023-6258?

CVE-2023-6258 is a high-severity vulnerability in Fedora, published on 30 Jan 2024. 

### Official description

A security vulnerability has been identified in the pkcs11-provider, which is associated with Public-Key Cryptography Standards (PKCS#11). If exploited successfully, this vulnerability could result in a Bleichenbacher-like security flaw, potentially enabling a side-channel attack on PKCS#1 1.5 decryption.

Weakness: CWE-203 (Observable Discrepancy), CWE-1300 (Improper Protection of Physical Side Channels)

## Which versions are affected by CVE-2023-6258?

It affects 1 product.


Products: Latchset Pkcs11-Provider.

## How do I fix CVE-2023-6258?

Upgrade to a fixed version.

## Is CVE-2023-6258 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6258 and fix it if it is affected.

What it is: CVE-2023-6258 is a high-severity vulnerability in Fedora, published on 30 Jan 2024. 
Exploitation: There is no known exploitation of CVE-2023-6258 in the wild and no public exploit code.

Affected product: Fedora. 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-2023-6258/ (Markdown: https://insights.sbomify.com/CVE-2023-6258/index.md)
```

## Sources

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

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