# ALBA-2019:3785: libcacard bug fix and enhancement update

> An update to libcacard fixes a bug related to key caching that broke CI usage, requiring users to upgrade packages.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 7 Nov 2019

## What is ALBA-2019:3785?

ALBA-2019:3785 is a vulnerability in libcacard, published on 7 Nov 2019. 

### Official description

The libcacard packages contain the Common Access Card (CAC) emulation library.

This update fixes the following bug:

* Backport the patch removing key caching to unbreak libcacard for CI usage (BZ#1750477).

Users of libcacard are advised to upgrade to these updated packages, which fix this bug.

## Which versions are affected by ALBA-2019:3785?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libcacard` | AlmaLinux:8 | All versions | 3:2.7.0-2.el8_1 |
| `libcacard-devel` | AlmaLinux:8 | All versions | 3:2.7.0-2.el8_1 |

## How do I fix ALBA-2019:3785?

Upgrade to a fixed version.

## Is ALBA-2019:3785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2019:3785 is a vulnerability in libcacard, published on 7 Nov 2019. 
Exploitation: There is no known exploitation of ALBA-2019:3785 in the wild and no public exploit code.

Affected product: libcacard. 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-2019-3785/ (Markdown: https://insights.sbomify.com/ALBA-2019-3785/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:3785

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