Vulnerability record · CVE-2021-3521 · published 22 August 2022
CVE-2021-3521: Rpm improper verification of cryptographic signature vulnerability
Rpm · Rpm
There is a flaw in RPM's signature functionality. OpenPGP subkeys are associated with a primary key via a "binding signature." RPM does not check the binding signature of subkeys prior to importing them. If an attacker is able to add or socially engineer another party to add a malicious subkey to a legitimate public key, RPM could wrongly trust a malicious signature. The greatest impact of this flaw is to data integrity. To exploit this flaw, an attacker must either compromise an RPM repository or convince an administrator to install an untrusted RPM or public key. It is strongly recommended to only use RPMs and public keys from trusted sources.
Description
There is a flaw in RPM's signature functionality. OpenPGP subkeys are associated with a primary key via a "binding signature." RPM does not check the binding signature of subkeys prior to importing them. If an attacker is able to add or socially engineer another party to add a malicious subkey to a legitimate public key, RPM could wrongly trust a malicious signature. The greatest impact of this flaw is to data integrity. To exploit this flaw, an attacker must either compromise an RPM repository or convince an administrator to install an untrusted RPM or public key. It is strongly recommended to only use RPMs and public keys from trusted sources.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://access.redhat.com/security/cve/CVE-2021-3521 | Third Party Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=1941098 | Issue TrackingPatchThird Party Advisory |
| https://github.com/rpm-software-management/rpm/commit/bd36c5dc9fb6d90c46fbfed8c2d67516fc571ec8 | PatchThird Party Advisory |
| https://github.com/rpm-software-management/rpm/pull/1795/ | PatchThird Party Advisory |
| https://security.gentoo.org/glsa/202210-22 | Third Party Advisory |
| https://access.redhat.com/security/cve/CVE-2021-3521 | Third Party Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=1941098 | Issue TrackingPatchThird Party Advisory |
| https://github.com/rpm-software-management/rpm/commit/bd36c5dc9fb6d90c46fbfed8c2d67516fc571ec8 | PatchThird Party Advisory |
| https://github.com/rpm-software-management/rpm/pull/1795/ | PatchThird Party Advisory |
| https://security.gentoo.org/glsa/202210-22 | Third Party Advisory |
Track CVE-2021-3521 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2021-3521), CISA KEV, FIRST EPSS (scores of 2026-10-17). This page is refreshed as NVD updates the record.