Scanning-process crash via unsigned bounds check
Published May 13, 2020 · Updated Nov 15, 2024
Heap buffer over-read in the ARJ parser in ClamAV before 0.102.3 allows remote attackers to crash the scanning process. The parser improperly bounds-checks an unsigned variable while processing a crafted ARJ archive, causing an out-of-bounds read. No authentication or user interaction is required when attacker-supplied archives reach a scanning workflow; impact is limited to process termination.
Summary
What happened
Heap buffer over-read in the ARJ parser in ClamAV before 0.102.3 allows remote attackers to crash the scanning process. The parser improperly bounds-checks an unsigned variable while processing a crafted ARJ archive, causing an out-of-bounds read. No authentication or user interaction is required when attacker-supplied archives reach a scanning workflow; impact is limited to process termination.
The record
- CVE
- CVE-2020-3327
- Published
- May 13, 2020
- Updated
- Nov 15, 2024
- Vendor
- ClamAV
- Product
- ClamAV
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2020CVE publishedPublication date reported by the CVE source.
- Nov 15, 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=unspecified <0.102.3
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.
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