Application crash via unchecked zero-size text buffer
Published Jun 30, 2021 · Updated Aug 3, 2024
Out-of-bounds write in DjVuLibre before 3.5.28 allows context-dependent attackers to crash a processing application via a crafted DjVu file. DJVU::DjVuTXT::decode() accepts a zero-length UTF-8 string whose getbuf() result is null, then writes a terminator to buffer[readsize] without checking the pointer. A victim must open or otherwise process the file; the demonstrated consequence is a segmentation fault and application crash, with no published data disclosure or code execution.
Summary
What happened
Out-of-bounds write in DjVuLibre before 3.5.28 allows context-dependent attackers to crash a processing application via a crafted DjVu file. DJVU::DjVuTXT::decode() accepts a zero-length UTF-8 string whose getbuf() result is null, then writes a terminator to buffer[readsize] without checking the pointer. A victim must open or otherwise process the file; the demonstrated consequence is a segmentation fault and application crash, with no published data disclosure or code execution.
The record
- CVE
- CVE-2021-3630
- Published
- Jun 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- DjVuLibre Project
- Product
- DjVuLibre
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 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=DjVuLibre 3.5.28
What conditions does exploitation require?
What is affected?
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
- djvutxt crash inputproof of concept · demonstrated
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