Package-processing crash via ar member-name underflow
Published May 15, 2020 · Updated Sep 17, 2024
Out-of-bounds read in Debian APT before 2.1.2 allows local users to crash package processing with a crafted deb file. In apt-pkg/contrib/arfile.cc, name normalization decrements past offset zero when an ar member name contains only spaces or slashes, then reads beyond the stack buffer. Processing an attacker-supplied deb file is required; the bounded consequence is a package-management process crash, with no reported data disclosure or modification.
Summary
What happened
Out-of-bounds read in Debian APT before 2.1.2 allows local users to crash package processing with a crafted deb file. In apt-pkg/contrib/arfile.cc, name normalization decrements past offset zero when an ar member name contains only spaces or slashes, then reads beyond the stack buffer. Processing an attacker-supplied deb file is required; the bounded consequence is a package-management process crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2020-3810
- Published
- May 15, 2020
- Updated
- Sep 17, 2024
- Vendor
- Debian
- Product
- APT
- Classifications
- CWE-125, CWE-20, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=before 2.1.2
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