CVE-2022-43705 [Critical] | Security Vulnerability in Botan

CVE-2022-43705 is rated Moderate Risk (50.8/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.19%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-12-10	0.26%	0.19%	-0.07%
2	2025-12-06	0.11%	0.26%	+0.15%
3	2025-11-21	—	0.11%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-12-10

0.26%

0.19%

-0.07%

2025-12-06

0.11%

0.26%

+0.15%

2025-11-21

—

0.11%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.1	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	3.9	5.2	[email protected]
9.1	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.2	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.1

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

3.9

5.2

[email protected]

9.1

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.2

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-43705

vendor	priority	summary	link
`alpine`	—	CVE-2022-43705: 1 source package rows (botan); 25 state rows across 4 repos (3.19-main, 3.20-main, 3.21-main, edge-main); fixed 0, open 25.	https://security.alpinelinux.org/vuln/CVE-2022-43705
`debian`	not yet assigned	CVE-2022-43705 not yet assigned priority: Debian including 1 source packages (botan), 3 status rows across 3 suites (bookworm, bullseye, trixie): resolved 2, open 1.	https://security-tracker.debian.org/tracker/CVE-2022-43705
`ubuntu`	medium	CVE-2022-43705 medium priority: Ubuntu including 1 source packages (botan), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 5, ignored 4, needed 3, released 1.	https://ubuntu.com/security/CVE-2022-43705

Affected software / configurations for CVE-2022-43705

Vendor	Product	Version	Raw CPE
botan_project	botan	>= 1.11.34, < 2.19.3	cpe:2.3:a:botan_project:botan::::::::

References for CVE-2022-43705

URL	Tags
https://github.com/randombit/botan/releases/tag/2.19.3	Release Notes Third Party Advisory
https://github.com/randombit/botan/security/advisories/GHSA-4v9w-qvcq-6q7w	Mitigation Third Party Advisory

URL

CVE-2022-43705

Exploit prediction scoring system (EPSS) score for CVE-2022-43705

Common vulnerability scoring system (CVSS) metrics for CVE-2022-43705

Weakness enumeration for CVE-2022-43705

OS Trackers for CVE-2022-43705

Affected software / configurations for CVE-2022-43705

References for CVE-2022-43705