dbcve.org
Openoffice.orgApplication · Openoffice

CVE-2007-5746

MEDIUM · 6.8 CVSS v2.0 Published 2008-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Integer overflow in OpenOffice.org before 2.4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via an EMF file with a crafted EMR_STRETCHBLT record, which triggers a heap-based buffer overflow.

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

Integer overflow vulnerability in OpenOffice.org versions prior to 2.4 when parsing EMF (Enhanced Metafile) image files. The flaw exists in the EMR_STRETCHBLT record handling, where crafted values trigger an integer overflow leading to a heap-based buffer overflow, potentially allowing arbitrary code execution or denial of service.

MitigationUpgrade OpenOffice.org to version 2.4 or later. Alternatively, implement file type restrictions and sandboxing to block or limit processing of untrusted EMF files until the patch can be applied.

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
Openoffice.orgApplication
Affected:= 2.0.3= 2.1= 2.2= 2.2.1= 2.3= 2.3.1

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
Partial
Integrity
Partial
Availability
Partial

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

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. Check if OpenOffice.org is installed
    Run command 'which soffice' or 'rpm -qa | grep -i openoffice' (Red Hat) or 'dpkg -l | grep -i openoffice' (Debian)
    Affected if No OpenOffice.org installation found means not affected by this specific CVE
  2. Determine installed OpenOffice.org version
    Run 'soffice --version' or check package manager output from previous step
    Affected if Version matches 2.0.3, 2.1, 2.2, 2.2.1, 2.3, or 2.3.1 - if your version is one of these, you are within the affected range
  3. Verify EMF file import capability is enabled
    Check OpenOffice.org configuration: look for EMF/EMF+ import filters in Tools > Options > Load/Save > File Formats, or inspect config files in user profile under 'filter' directories
    Affected if EMF import filter is present and enabled - the vulnerability only triggers when OpenOffice parses an EMF file
  4. Check for recent EMF file processing activity
    Review user activity logs, recent documents list, or mail filters for EMF attachments that may have been opened in OpenOffice
    Affected if Users have recently opened untrusted EMF files in OpenOffice - exploitation requires processing a crafted EMF file

You are affected if OpenOffice.org versions 2.0.3 through 2.3.1 are installed AND the EMF import filter is enabled AND users process untrusted EMF files.

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

Upgrade OpenOffice.org to version 2.4 or later. Alternatively, implement file type restrictions and sandboxing to block or limit processing of untrusted EMF files until the patch can be applied.

Fix this in Openoffice.org Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5746 — 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-5746 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