dbcve.org
OpenofficeApplication

CVE-2007-0239

HIGH · 9.3 CVSS v2.0 Published 2007-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenOffice.org (OOo) Office Suite allows user-assisted remote attackers to execute arbitrary commands via shell metacharacters in a prepared link in a crafted document.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenOffice.org fails to properly sanitize shell metacharacters in links embedded within crafted documents. When a user opens a malicious document and interacts with a prepared link, the shell metacharacters are passed to the underlying operating system for execution, allowing arbitrary command execution.

MitigationUsers should not open untrusted documents from unknown sources. Organizations should update OpenOffice.org to a patched version that properly sanitizes link parameters and blocks shell metacharacter interpretation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenofficeApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify OpenOffice.org installation
    Check if OpenOffice.org is installed by looking for the application binary or package. On Linux, run 'which soffice' or check /usr/bin/soffice. On Windows, check Program Files for OpenOffice folder.
    Affected if OpenOffice.org is found installed on the system
  2. Determine installed OpenOffice.org version
    Run 'soffice --version' on Linux or check the About dialog in the application. Record the full version number (e.g., 2.3.0, 2.4.0).
    Affected if The installed version is any version of OpenOffice.org (the CVE states all versions are affected)
  3. Check for shell metacharacter handling in hyperlinks
    Create a test document with a hyperlink containing shell metacharacters (such as ;ls or |whoami). Open the document in OpenOffice and attempt to interact with the link. Observe if the metacharacters are passed to the operating system.
    Affected if The shell metacharacters in the hyperlink are executed by the OS when the link is clicked (indicates the vulnerability is present)
  4. Verify document handling policy
    Review whether the system processes documents from untrusted or unknown sources, particularly those containing hyperlinks.
    Affected if Users routinely open documents from untrusted sources without additional security controls

If OpenOffice.org is installed and users open documents from untrusted sources, the environment is likely affected since all versions of OpenOffice.org were reported as vulnerable to shell metacharacter injection in embedded links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should not open untrusted documents from unknown sources. Organizations should update OpenOffice.org to a patched version that properly sanitizes link parameters and blocks shell metacharacter interpretation.

Fix this in Openoffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0239 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data