# ALBA-2021:3054: opencryptoki bug fix and enhancement update

> The opencryptoki soft token fails to validate EC keys, allowing potential security bypasses in cryptographic operations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2021

## What is ALBA-2021:3054?

ALBA-2021:3054 is a missing authorization vulnerability in opencryptoki-devel, published on 10 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The opencryptoki packages contain version 2.11 of the PKCS#11 API,
implemented for IBM Cryptocards, such as IBM 4764 and 4765 crypto cards.
These packages includes support for the IBM 4758 Cryptographic CoProcessor
(with the PKCS#11 firmware loaded), the IBM eServer Cryptographic
Accelerator (FC 4960 on IBM eServer System p), the IBM Crypto Express2 (FC
0863 or FC 0870 on IBM System z), and the IBM CP Assist for Cryptographic
Function (FC 3863 on IBM System z). The opencryptoki packages also bring a
software token implementation that can be used without any cryptographic
hardware. These packages contain the Slot Daemon (pkcsslotd) and general
utilities.

Bug Fix(es) and Enhancement(s):

* AlmaLinux8.5 - openCryptoki: Soft token does not check if an EC key is valid
(BZ#1979173)

## Which versions are affected by ALBA-2021:3054?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opencryptoki-devel` | AlmaLinux:8 | All versions | 3.15.1-6.el8_4 |

## How do I fix ALBA-2021:3054?

Apply the vendor's patch.

## Is ALBA-2021:3054 being exploited?

There is no known exploitation of ALBA-2021:3054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2021:3054 and fix it if it is affected.

What it is: ALBA-2021:3054 is a missing authorization vulnerability in opencryptoki-devel, published on 10 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2021:3054 in the wild and no public exploit code.

Affected product: opencryptoki-devel. 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/ALBA-2021-3054/ (Markdown: https://insights.sbomify.com/ALBA-2021-3054/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:3054

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