# ALBA-2021:3573: ca-certificates bug fix and enhancement update

> This update provides annual CA certificate refreshes for AlmaLinux, ensuring trust store integrity without addressing a specific exploitable vulnerability.

- **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:** 21 Sep 2021

## What is ALBA-2021:3573?

ALBA-2021:3573 is a vulnerability in ca-certificates, published on 21 Sep 2021. 

### Official description

The ca-certificates package contains a set of Certificate Authority (CA)
certificates chosen by the Mozilla Foundation for use with the Internet
Public Key Infrastructure (PKI).

Bug Fix(es) and Enhancement(s):

* Annual 2021 ca-certificates update 2.48 from nss 3.66 for Firefox 91
(BZ#1971200)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ca-certificates` | AlmaLinux:8 | All versions | 2021.2.50-80.0.el8_4 |

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

Upgrade to a fixed version.

## Is ALBA-2021:3573 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:3573 is a vulnerability in ca-certificates, published on 21 Sep 2021. 
Exploitation: There is no known exploitation of ALBA-2021:3573 in the wild and no public exploit code.

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

## Sources

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

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