CVE-2021-3569

A stack corruption bug was found in libtpms in versions before 0.7.2 and before 0.8.0 while decrypting data using RSA. This flaw could result in a SIGBUS (bad memory access) and termination of swtpm. The highest threat from this vulnerability is to system availability.

Published: 2021-06-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-3569 is rated Low Risk (28.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.26%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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

Exploit prediction scoring system (EPSS) score for CVE-2021-3569

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.05% 0.26% +0.21%
2 2025-10-08 0.13% 0.05% -0.08%
3 2025-03-17 — 0.13% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-3569

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:L)
A normal user session is enough; they don’t have to be admin.
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.
 1.8 3.6 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2021-3569

OS Trackers for CVE-2021-3569

vendor priority summary link
debian not yet assigned CVE-2021-3569 not yet assigned priority: Debian including 1 source packages (libtpms), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 4. https://security-tracker.debian.org/tracker/CVE-2021-3569
redhat medium — https://access.redhat.com/security/cve/CVE-2021-3569
suse medium — https://www.suse.com/security/cve/CVE-2021-3569/
ubuntu medium CVE-2021-3569 medium priority: Ubuntu including 1 source packages (libtpms), 9 status rows across 9 suites (bionic, focal, groovy, hirsute, impish, jammy, trusty, upstream, xenial): DNE 3, ignored 3, not-affected 2, released 1. https://ubuntu.com/security/CVE-2021-3569

Affected software / configurations for CVE-2021-3569

Vendor Product Version Raw CPE
libtpms_project libtpms < 0.7.2 cpe:2.3:a:libtpms_project:libtpms:*:*:*:*:*:*:*:*
libtpms_project libtpms >= 0.7.3, < 0.8.0 cpe:2.3:a:libtpms_project:libtpms:*:*:*:*:*:*:*:*
redhat enterprise_linux 8.0 cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:advanced_virtualization:*:*:*

References for CVE-2021-3569

URL Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1964358 Issue Tracking Patch Third Party Advisory
cvelogic Threat Intelligence