First published: Fri Mar 19 2021(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Rpm Rpm | <4.17.1 |
https://github.com/rpm-software-management/rpm/commit/bd36c5dc9fb6d90c46fbfed8c2d67516fc571ec8
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-3521 is a vulnerability in RPM's signature functionality that allows an attacker to add a malicious subkey.
CVE-2021-3521 has a severity rating of 4.7, which is considered medium.
CVE-2021-3521 works by bypassing the check for the binding signature of OpenPGP subkeys, allowing the import of malicious subkeys.
RPM version up to and excluding 4.17.1 is affected by CVE-2021-3521.
Yes, a fix for CVE-2021-3521 is available. Please refer to the provided references for more information.