CVE-2022-48570

Exp

Crypto++ through 8.4 contains a timing side channel in ECDSA signature generation. Function FixedSizeAllocatorWithCleanup could write to memory outside of the allocation if the allocated memory was not 16-byte aligned. NOTE: this issue exists because the CVE-2019-14318 fix was intentionally removed for functionality reasons.

Published: 2023-08-22 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-48570 is rated High Exploit Risk (63.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.82%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-48570

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.65% 0.82% +0.17%
2 2026-05-17 0.52% 0.65% +0.13%
3 2025-11-21 — 0.52% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:N)
Doesn’t really leak secrets in a meaningful 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 3.6 [email protected]

Weakness enumeration for CVE-2022-48570

OS Trackers for CVE-2022-48570

vendor priority summary link
debian not yet assigned CVE-2022-48570 not yet assigned priority: Debian including 1 source packages (libcrypto++), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2022-48570
ubuntu medium CVE-2022-48570 medium priority: Ubuntu including 1 source packages (libcrypto++), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 4. https://ubuntu.com/security/CVE-2022-48570

Affected software / configurations for CVE-2022-48570

Vendor Product Version Raw CPE
cryptopp crypto\+\+ <= 8.4.0 cpe:2.3:a:cryptopp:crypto\+\+:*:*:*:*:*:*:*:*

References for CVE-2022-48570

cvelogic Threat Intelligence