Package database corruption via unchecked signature tags
Published Mar 26, 2021 · Updated Aug 3, 2024
Signature verification bypass in RPM Package Manager allows attackers to corrupt the package database through a modified signed package. headerMergeLegacySigs() copies unknown signature-header tags into package metadata without validating each tag's expected type and size. Exploitation requires a compromised repository or an administrator installing an untrusted package; resulting corruption can hide installed packages and dependencies but is repairable.
Summary
What happened
Signature verification bypass in RPM Package Manager allows attackers to corrupt the package database through a modified signed package. headerMergeLegacySigs() copies unknown signature-header tags into package metadata without validating each tag's expected type and size. Exploitation requires a compromised repository or an administrator installing an untrusted package; resulting corruption can hide installed packages and dependencies but is repairable.
The record
- CVE
- CVE-2021-20271
- Published
- Mar 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- RPM Software Management
- Product
- RPM Package Manager
- Classifications
- CWE-345, T1195.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all versions
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo