# CVE-2021-24115: Information disclosure in n/a

> Attackers can potentially recover sensitive data via timing side-channels in Botan's base32, base58, base64, and hex encoding/decoding operations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2021-24115, AZL-44961, DEBIAN-CVE-2021-24115, GHSA-cj2q-f8cp-cqmf, MGASA-2021-0329, UBUNTU-CVE-2021-24115, openSUSE-SU-2021:0765-1, openSUSE-SU-2021:0794-1

## What is CVE-2021-24115?

CVE-2021-24115 is a critical vulnerability in n/a, published on 22 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and hex).

## Which versions are affected by CVE-2021-24115?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Botan` | SUSE:Package Hub 15 SP1 | All versions | 2.10.0-bp152.4.3.1 |
| `Botan` | SUSE:Package Hub 15 SP2 | All versions | 2.10.0-bp152.4.3.1 |
| `Botan` | SUSE:Package Hub 15 SP2 | All versions | 2.10.0-bp152.4.6.1 |
| `Botan` | openSUSE:Leap 15.2 | All versions | 2.10.0-bp152.4.3.1 |

Products: Botan Project Botan.

## How do I fix CVE-2021-24115?

Upgrade to a fixed version.

## Is CVE-2021-24115 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-9127](https://insights.sbomify.com/CVE-2018-9127/): Security feature bypass in n/a (critical 9.8)
- [CVE-2015-7826](https://insights.sbomify.com/CVE-2015-7826/): Security feature bypass in n/a (critical 9.8)
- [CVE-2016-6878](https://insights.sbomify.com/CVE-2016-6878/): Other in n/a (critical 9.8)
- [CVE-2016-9132](https://insights.sbomify.com/CVE-2016-9132/): Integer overflow in n/a (critical 9.8)
- [CVE-2016-2195](https://insights.sbomify.com/CVE-2016-2195/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24115 and fix it if it is affected.

What it is: CVE-2021-24115 is a critical vulnerability in n/a, published on 22 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24115 in the wild and no public exploit code.

Affected product: n/a. 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-2021-24115/ (Markdown: https://insights.sbomify.com/CVE-2021-24115/index.md)
```

## Sources

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

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