Loading vulnerability…
A heap-based buffer overflow exists in the OLE importer component of OpenOffice.org versions prior to 2.4. The vulnerability is triggered when the application processes an OLE file containing a specially crafted DocumentSummaryInformation stream. This flaw allows remote attackers to cause a denial of service (application crash) and potentially execute arbitrary code within the context of the user running OpenOffice.org.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/openoffice_ole.rb) that exploits a buffer overflow vulnerability (CVE-2008-0320) in OpenOffice 2.3.0 and 2.3.1 on Windows XP SP3. The exploit works by generating a malicious OLE file (default name: msf.doc) with a malformed DocumentSummaryInformation stream. When a user opens this file in a vulnerable version of OpenOffice, arbitrary code execution is achieved under the user's context. The module allows the attacker to inject a customizable Metasploit payload into the file at specific offsets. The attack vector is local, requiring the victim to open the crafted file. The module references a template file (data/exploits/CVE-2008-0320.doc) as the basis for the malicious document. No network endpoints are involved; the exploit is file-based. The code is written in Ruby and is operational, allowing for payload customization within the Metasploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.