Openoffice vulnerabilitiesRanked by how likely they are to be used.

Product44 versions
The short answer

Openoffice is made by Apache. We track 55 published vulnerabilities in it, across 44 versions. None of them is on the list of flaws known to be exploited today. If you run Openoffice, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Openoffice vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Openoffice's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Openoffice flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 78%

    An information disclosure vulnerability occurs when LibreOffice 6.0.3 and Apache OpenOffice Writer 4.1.5 automatically process and initiate an SMB connection embedded in a malicious file, as demonstrated by...

    CVSS7.5Published1 May 2018
  2. 51%

    Apache OpenOffice opens dBase/DBF documents and shows the contents as spreadsheets.

    CVSS7.8Published23 Sep 2021
  3. 15%

    Apache OpenOffice before 4.1.1 allows remote attackers to execute arbitrary commands and possibly have other unspecified impact via a crafted Calc spreadsheet.

    CVSS9.3Published26 Aug 2014
  4. 14%

    Integer overflow in the XPMReader::ReadXPM function in filter.vcl/ixpm/svt_xpmread.cxx in OpenOffice.org (OOo) before 3.2 allows remote attackers to execute arbitrary code via a crafted XPM file that triggers a...

    CVSS9.3Published16 Feb 2010
  5. 14%

    LibreOffice before 4.4.5 and Apache OpenOffice before 4.1.2 uses the stored LinkUpdateMode configuration information in OpenDocument Format files and templates when handling links, which might allow remote attackers...

    CVSS4.3Published10 Nov 2015
  6. 14%

    Heap-based buffer overflow in the GIFLZWDecompressor::GIFLZWDecompressor function in filter.vcl/lgif/decode.cxx in OpenOffice.org (OOo) before 3.2 allows remote attackers to cause a denial of service (application...

    CVSS9.3Published16 Feb 2010
  7. 13%

    Integer overflow in LibreOffice before 4.4.5 and Apache OpenOffice before 4.1.2 allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via a...

    CVSS6.8Published10 Nov 2015
  8. 12%

    Integer underflow in filter/ww8/ww8par2.cxx in OpenOffice.org (OOo) before 3.2 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted sprmTDefTable...

    CVSS9.3Published16 Feb 2010
Precursor Intelligence

Running Openoffice? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 55 published vulnerabilities listed under the name Openoffice, across 44 versions.

None of Openoffice's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Openoffice. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.