# ALBA-2021:3049: pcsc-lite bug fix and enhancement update

> An update to pcsc-lite increases the reader array size to prevent issues with secure channel creation, potentially avoiding service disruptions.

- **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:** 10 Aug 2021

## What is ALBA-2021:3049?

ALBA-2021:3049 is a vulnerability in pcsc-lite-ccid, published on 10 Aug 2021. 

### Official description

PC/SC Lite provides a Windows SCard compatible interface for communicating
with smart cards, smart card readers, and other security tokens.

Bug Fixes:

* Increase global reader array size to 48 to address issue with RHCS secure
channel creation (BZ#1972569)

* Increase global reader array size to 48 to address issue with RHCS secure
channel creation (pcsc-lite-ccid) (BZ#1973405)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pcsc-lite-ccid` | AlmaLinux:8 | All versions | 1.4.29-5.1.el8_4 |
| `pcsc-lite-devel` | AlmaLinux:8 | All versions | 1.8.23-4.1.el8_4 |

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

Apply the vendor's patch.

## Is ALBA-2021:3049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:3049 is a vulnerability in pcsc-lite-ccid, published on 10 Aug 2021. 
Exploitation: There is no known exploitation of ALBA-2021:3049 in the wild and no public exploit code.

Affected product: pcsc-lite-ccid. 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-3049/ (Markdown: https://insights.sbomify.com/ALBA-2021-3049/index.md)
```

## Sources

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

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