Arbitrary .ttf file write via embedded font paths
Published Jan 7, 2025 · Updated Nov 3, 2025
Path traversal in LibreOffice 24.8 before 24.8.4 allows attackers to write embedded font data to writable locations via a crafted document. The embedded-font extractor trusts path names stored in supported document formats instead of confining extracted fonts to temporary files, while appending .ttf to the chosen path. Exploitation requires the document to be opened, and writes remain limited to locations writable with the LibreOffice user's permissions and filenames ending in .ttf.
Summary
What happened
Path traversal in LibreOffice 24.8 before 24.8.4 allows attackers to write embedded font data to writable locations via a crafted document. The embedded-font extractor trusts path names stored in supported document formats instead of confining extracted fonts to temporary files, while appending .ttf to the chosen path. Exploitation requires the document to be opened, and writes remain limited to locations writable with the LibreOffice user's permissions and filenames ending in .ttf.
The record
- CVE
- CVE-2024-12425
- Published
- Jan 7, 2025
- Updated
- Nov 3, 2025
- Vendor
- The Document Foundation
- Product
- LibreOffice
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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.8 << 24.8.4
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