Staroffice vulnerabilitiesRanked by how likely they are to be used.
Staroffice is made by Sun. We track 10 published vulnerabilities in it, across 5 versions. None of them is on the list of flaws known to be exploited today. If you run Staroffice, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Staroffice vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Staroffice's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Staroffice 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.
- 12%CVE-2007-2834Critical
Integer overflow in the TIFF parser in OpenOffice.org (OOo) before 2.3; and Sun StarOffice 6, 7, and 8 Office Suite (StarSuite); allows remote attackers to execute arbitrary code via a TIFF file with crafted values...
- 8.5%CVE-2006-5870Critical
Multiple integer overflows in OpenOffice.org (OOo) 2.0.4 and earlier, and possibly other versions before 2.1.0; and StarOffice 6 through 8; allow user-assisted remote attackers to execute arbitrary code via a crafted...
- 5.9%CVE-2000-0174Medium
StarOffice StarScheduler web server allows remote attackers to read arbitrary files via a ..
- 4.3%CVE-2006-3117High
Heap-based buffer overflow in OpenOffice.org (aka StarOffice) 1.1.x up to 1.1.5 and 2.0.x before 2.0.3 allows user-assisted attackers to execute arbitrary code via a crafted OpenOffice XML document that is not...
- 3.5%CVE-2006-2198High
OpenOffice.org (aka StarOffice) 1.1.x up to 1.1.5 and 2.0.x before 2.0.3 allows user-assisted attackers to conduct unauthorized activities via an OpenOffice document with a malicious BASIC macro, which is executed...
- 3.5%CVE-2006-2199High
Unspecified vulnerability in Java Applets in OpenOffice.org 1.1.x (aka StarOffice) up to 1.1.5 and 2.0.x before 2.0.3 allows user-assisted attackers to escape the Java sandbox and conduct unauthorized activities via...
- 2.4%CVE-2000-0175Critical
Buffer overflow in StarOffice StarScheduler web server allows remote attackers to gain root access via a long GET command.
- 0.5%
StarOffice 5.2 follows symlinks and sets world-readable permissions for the /tmp/soffice.tmp directory, which allows a local user to read files of the user who is using StarOffice.
- 0.4%CVE-2000-0291Medium
Buffer overflow in Star Office 5.1 allows attackers to cause a denial of service by embedding a long URL within a document.
Running Staroffice? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 new flaw affects software Acme tracks
Integer overflow in the TIFF parser in OpenOffice.org (OOo) before 2.3; and Sun StarOffice 6, 7, and 8 Office Suite (StarSuite); allows remote attackers to execute arbitrary code via a TIFF file with crafted values of unspecified length fields, which triggers allocation of an incorrect amount of memory, resulting in a heap-based buffer overflow.
- Matched to
- Staroffice on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 10 published vulnerabilities listed under the name Staroffice, across 5 versions.
None of Staroffice's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Staroffice. 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.