Improper Verification of Cryptographic Signature Affecting rpm-plugin-fapolicyd package, versions <0:4.14.3-19.el8_5.2


Severity

Recommended
0.0
medium
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.07% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX8-RPMPLUGINFAPOLICYD-5613854
  • published28 May 2023
  • disclosed1 Feb 2022

Introduced: 1 Feb 2022

CVE-2021-3521  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 rpm-plugin-fapolicyd to version 0:4.14.3-19.el8_5.2 or higher.
This issue was patched in ALSA-2022:0368.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rpm-plugin-fapolicyd package and not the rpm-plugin-fapolicyd package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

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 Scores

version 3.1