Vulnerabilities · 2021 · Rpm
CVE-2021-3521
Rpm vulnerability
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.
Affected products
Rpm. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Rpm runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugzilla.redhat.com/show_bug.cgi?id=1941098 · Patch
- github.com/rpm-software-management/rpm/commit/bd36c5dc9fb6d90c46fbfed8c2d67516fc571ec8 · Patch
- github.com/rpm-software-management/rpm/pull/1795/ · Patch
- access.redhat.com/security/cve/CVE-2021-3521 · Third Party Advisory
- security.gentoo.org/glsa/202210-22 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2021-3521
- cve.org/CVERecord?id=CVE-2021-3521
More vulnerabilities in Rpm products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.