rpm: RPM does not require subkeys to have a valid binding signature
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | RPM | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| rpm-0:4.14.3-19.el8_5.2 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2022:0368 | 2022-02-01T00:00:00Z |
| rpm-0:4.14.3-19.el8_5.2 | cpe:/o:redhat:enterprise_linux:8 | RHSA-2022:0368 | 2022-02-01T00:00:00Z |
| Red Hat Enterprise Linux 8.2 Extended Update Support | |||
| rpm-0:4.14.2-40.el8_2 | cpe:/a:redhat:rhel_eus:8.2 | RHSA-2022:0634 | 2022-02-22T00:00:00Z |
| Red Hat Enterprise Linux 8.4 Extended Update Support | |||
| rpm-0:4.14.3-14.el8_4.2 | cpe:/a:redhat:rhel_eus:8.4 | RHSA-2022:0254 | 2022-01-25T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-26837 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.325% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.