# CVE-2022-43705: Security feature bypass in n/a

> Attackers can forge OCSP responses due to a certificate verification error in the Botan library, bypassing revocation checks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 27 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** AZL-44751, DEBIAN-CVE-2022-43705, GHSA-4v9w-qvcq-6q7w, MGASA-2022-0445, UBUNTU-CVE-2022-43705, openSUSE-SU-2022:10210-1, openSUSE-SU-2022:10211-1, openSUSE-SU-2024:12522-1

## What is CVE-2022-43705?

CVE-2022-43705 is a critical vulnerability in n/a, published on 27 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error. This issue was introduced in Botan 1.11.34 (November 2016).

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-43705?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Botan` | SUSE:Package Hub 15 SP3 | All versions | 2.10.0-bp153.3.3.1 |
| `Botan` | SUSE:Package Hub 15 SP4 | All versions | 2.18.2-bp154.2.3.1 |
| `Botan` | openSUSE:Leap 15.3 | All versions | 2.10.0-bp153.3.3.1 |
| `Botan` | openSUSE:Leap 15.4 | All versions | 2.18.2-bp154.2.3.1 |
| `Botan` | openSUSE:Tumbleweed | All versions | 2.19.3-1.1 |

Products: Botan Project Botan.

## How do I fix CVE-2022-43705?

Upgrade to a fixed version.

## Is CVE-2022-43705 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-24115](https://insights.sbomify.com/CVE-2021-24115/): Information disclosure in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43705 and fix it if it is affected.

What it is: CVE-2022-43705 is a critical vulnerability in n/a, published on 27 Nov 2022. 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-2022-43705 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-2022-43705/ (Markdown: https://insights.sbomify.com/CVE-2022-43705/index.md)
```

## Sources

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

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