Homepage
About Snyk

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

0.0
medium

Snyk CVSS

    Attack Complexity High
    User Interaction Required
    Integrity High

    Threat Intelligence

    EPSS 0.07% (30th percentile)
Expand this section
NVD
4.7 medium
Expand this section
Red Hat
4.4 medium

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 ID SNYK-CENTOS8-PYTHON3RPM-1965899
  • published 30 Sep 2021
  • disclosed 28 Sep 2021
Report a new vulnerability Found a mistake?

Introduced: 28 Sep 2021

CVE-2021-3521 Open this link in a new tab
CWE-347 Open this link in a new tab

How to fix?

Upgrade Centos:8 python3-rpm to version 0:4.14.3-19.el8_5.2 or higher.

NVD Description

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