Signature forgery via ZIP repair reconstruction
Published Sep 17, 2024 · Updated Oct 12, 2024
Digital signature validation in LibreOffice 24.2 before 24.2.5 allows attackers to forge document trust via a crafted ZIP-based file. Repair mode reconstructs a corrupt ZIP central directory by scanning local file headers but then reports a signature status that does not authenticate the recovered content. Opening the crafted document and accepting repair is required, and the false status can mislead users about the integrity of recovered content.
Summary
What happened
Digital signature validation in LibreOffice 24.2 before 24.2.5 allows attackers to forge document trust via a crafted ZIP-based file. Repair mode reconstructs a corrupt ZIP central directory by scanning local file headers but then reports a signature status that does not authenticate the recovered content. Opening the crafted document and accepting repair is required, and the false status can mislead users about the integrity of recovered content.
The record
- CVE
- CVE-2024-7788
- Published
- Sep 17, 2024
- Updated
- Oct 12, 2024
- Vendor
- The Document Foundation
- Product
- LibreOffice
- Classifications
- CWE-347, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2024CVE publishedPublication date reported by the CVE source.
- Oct 12, 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=24.2 << 24.2.5
- Affected versionversion=24.2 <24.2.5
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