Improper Verification of Cryptographic Signature Affecting rpm-32bit package, versions <4.14.3-150400.59.16.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.07% (33rd 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-SLES156-RPM32BIT-7172724
  • published31 May 2024
  • disclosed30 May 2024

Introduced: 30 May 2024

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

How to fix?

Upgrade SLES:15.6 rpm-32bit to version 4.14.3-150400.59.16.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rpm-32bit package and not the rpm-32bit package as distributed by SLES. See How to fix? for SLES:15.6 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