Code execution via unchecked DBF field length
Published Sep 23, 2021 · Updated Aug 3, 2024
Classic buffer overflow in Apache OpenOffice 4.1.10 and earlier allows attackers to execute arbitrary code via a crafted DBF document. ODbaseTable::fetchRow copies attacker-controlled nLen bytes from DBF integer fields into a four-byte sal_Int32 local without validating the field length. The attack requires a user to open the document; successful exploitation overwrites the program stack and executes code in that user's context.
Summary
What happened
Classic buffer overflow in Apache OpenOffice 4.1.10 and earlier allows attackers to execute arbitrary code via a crafted DBF document. ODbaseTable::fetchRow copies attacker-controlled nLen bytes from DBF integer fields into a four-byte sal_Int32 local without validating the field length. The attack requires a user to open the document; successful exploitation overwrites the program stack and executes code in that user's context.
The record
- CVE
- CVE-2021-33035
- Published
- Sep 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache OpenOffice
- Classifications
- CWE-120, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 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=Apache OpenOffice <=4.1.10
- Affected versionversion=OpenOffice.org <=3.4
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
- All Your (d)Base Are Belong To Us, Part 1proof 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