Skip to content
Fencer Intel
critical 9.1

CVE-2022-43705 json

In Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error.

published 3y ago modified 4mo ago also EUVD-2022-46687

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

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).

Patch / fix

  • botan_project botan 2.19.3
  • botan Debian 13, Debian 12 2.19.3+dfsg-1

debian advisories DEBIAN-CVE-2022-43705

  • Botan openSUSE Tumbleweed 2.19.3-1.1
  • Botan Package Hub 15 SP4, openSUSE Leap 15.4 2.18.2-bp154.2.3.1
  • Botan Package Hub 15 SP3, openSUSE Leap 15.3 2.10.0-bp153.3.3.1

opensuse advisories openSUSE-SU-2024:12522-1openSUSE-SU-2022:10211-1openSUSE-SU-2022:10210-1

Is CVE-2022-43705 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-43705 updated cvss 6.5

botan: OCSP response falsification

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.