Vulnerability in Rpm
CVE-2021-3521
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.7 (Medium). Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS 0.003, 25.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Rpm
- Rpm — versions Fixed in rpm-4.18.0-beta1, rpm-4.18.0-alpha2, rpm-4.18.0-alpha1 .
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (ARPSyndicate/cvemon, ARPSyndicate/cve-scores). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- bugzilla.redhat.com/show_bug.cgi (Patch, Third Party Advisory, Issue Tracking)
- access.redhat.com/security/cve/CVE-2021-3521 (Third Party Advisory)
- github.com/rpm-software-management/rpm/pull/1795/ (Patch, Third Party Advisory)
- github.com/rpm-software-management/rpm/commit/bd36c5dc9fb6d90c46fbfed8c2d67516f… (Patch, Third Party Advisory)
- GLSA-202210-22 (vendor-advisory, Third Party Advisory)