CVE-2021-3521
CVSS V2 None
CVSS V3 Medium 4.7
Description
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.
Overview
- CVE ID
- CVE-2021-3521
- Assigner
- secalert@redhat.com
- Vulnerability Status
- Modified
- Published Version
- 2022-08-22T15:15:13
- Last Modified Date
- 2023-02-12T23:41:15
Weakness Enumerations
CPE Configuration (Product)
| CPE | Vulnerable | Operator | Version Start | Version End |
|---|---|---|---|---|
| cpe:2.3:a:rpm:rpm:*:*:*:*:*:*:*:* | 1 | OR | 4.17.1 |
CVSS Version 3
- Version
- 3.1
- Vector String
- CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
- Attack Vector
- LOCAL
- Attack Compatibility
- HIGH
- Privileges Required
- NONE
- User Interaction
- REQUIRED
- Scope
- UNCHANGED
- Confidentiality Impact
- NONE
- Availability Impact
- NONE
- Base Score
- 4.7
- Base Severity
- MEDIUM
- Exploitability Score
- 1
- Impact Score
- 3.6
References
| Reference URL | Reference Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2022:0254 | |
| https://access.redhat.com/errata/RHSA-2022:0368 | |
| https://access.redhat.com/errata/RHSA-2022:0634 | |
| https://access.redhat.com/security/cve/CVE-2021-3521 | Third Party Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=1941098 | Issue Tracking Patch Third Party Advisory |
| https://github.com/rpm-software-management/rpm/commit/bd36c5dc9fb6d90c46fbfed8c2d67516fc571ec8 | Patch Third Party Advisory |
| https://github.com/rpm-software-management/rpm/pull/1795/ | Patch Third Party Advisory |
| https://security.gentoo.org/glsa/202210-22 | Third Party Advisory |
Sources
| Source Name | Source URL |
|---|---|
| NIST | https://nvd.nist.gov/vuln/detail/CVE-2021-3521 |
| MITRE | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3521 |
History
| Created | Old Value | New Value | Data Type | Notes |
|---|---|---|---|---|
| 2022-08-22 16:00:12 | Added to TrackCVE | |||
| 2022-12-06 14:34:23 | 2022-12-03T01:25:09 | CVE Modified Date | updated | |
| 2022-12-06 14:34:23 | Undergoing Analysis | Analyzed | Vulnerability Status | updated |
| 2023-02-02 23:14:05 | 2023-02-02T21:21:06 | CVE Modified Date | updated | |
| 2023-02-02 23:14:05 | Analyzed | Modified | Vulnerability Status | updated |
| 2023-02-02 23:14:06 | 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. | There is a flaw in RPM's signature functionality. OpenPGP subkeys are associated with a primary key via a "binding signature."[1] 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. 1. https://tools.ietf.org/html/rfc4880#section-5.2.1 | Description | updated |
| 2023-02-02 23:14:07 | References | updated | ||
| 2023-02-13 00:14:47 | 2023-02-12T23:41:15 | CVE Modified Date | updated | |
| 2023-02-13 00:14:48 | There is a flaw in RPM's signature functionality. OpenPGP subkeys are associated with a primary key via a "binding signature."[1] 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. 1. https://tools.ietf.org/html/rfc4880#section-5.2.1 | 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. | Description | updated |