Content spoofing and macro execution via certificate doubling
Published Oct 11, 2021 · Updated Aug 4, 2024
Improper signature verification in Apache OpenOffice 4.1.10 and earlier allows attackers to forge trusted ODF documents and macros. During XML-signature validation, separate X.509 certificates can satisfy cryptographic verification and trust validation, so no single certificate must pass both checks. An attacker who obtains a signed ODF file can alter its content or replace protected macros while the application continues to display the signature as valid and trusted.
Summary
What happened
Improper signature verification in Apache OpenOffice 4.1.10 and earlier allows attackers to forge trusted ODF documents and macros. During XML-signature validation, separate X.509 certificates can satisfy cryptographic verification and trust validation, so no single certificate must pass both checks. An attacker who obtains a signed ODF file can alter its content or replace protected macros while the application continues to display the signature as valid and trusted.
The record
- CVE
- CVE-2021-41830
- Published
- Oct 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache OpenOffice
- Classifications
- CWE-347, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Certificate Doubling proof-of-concept demonstrationproof 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