Vulnerabilities for products matching "openoffice"
Found 2 matching products. Filters apply to all results.
You can search for specific versions with /product/openoffice/1.2.3
openoffice / openoffice
16 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
Low | June 16, 2008 6/16/08 |
== 1.1
|
|
|
|
Medium | April 17, 2008 4/17/08 |
<= 2.3.1
|
|
|
|
High | December 6, 2007 12/6/07 |
== 2.1
== 2.2
== 2.0.3_1
== 2.2.1
== 2.0.4
<= 2.3
== 2.0.3
== 2.0beta
== 2.0.1
== 2.0.2
|
|
|
|
Low | August 8, 2007 8/8/07 |
== 2.2
|
|
|
|
High | June 12, 2007 6/12/07 |
<= 2.2.1
|
|
|
|
High | March 21, 2007 3/21/07 |
*
|
|
|
|
High | March 21, 2007 3/21/07 |
*
|
|
|
|
High | December 31, 2006 12/31/06 |
<= 2.0.4
|
|
|
|
Low | December 18, 2006 12/18/06 |
== 2.1
|
|
|
|
High | June 30, 2006 6/30/06 |
== 2.0.0_rc3
== 2.0.0
== 2.0.3_rc4
== 1.1.1
== 1.1.2
== 2.0.3_rc3
== 2.0.2_rc2
== 2.0.2_rc3
== 2.0.0_rc2
== 2.0.0_rc1
== 2.0.3_rc5
== 1.1.4
== 2.0.3_rc6
== 1.1.0
== 2.0.2_rc4
== 2.0.1
== 1.1.3
== 1.1.1a
== 1.1.1b
== 1.1.5
== 2.0.2
== 2.0.2_rc1
|
|
|
|
High | June 30, 2006 6/30/06 |
== 2.0.0
== 1.1.1
== 1.1.2
== 1.1.4
== 1.1.0
== 2.0.1
== 1.1.3
== 1.1.5
== 2.0.2
|
|
|
|
High | June 30, 2006 6/30/06 |
== 2.0.0
== 1.1.1
== 1.1.2
== 2.0
== 1.1.4
== 1.1.0
== 2.0.1
== 1.1.3
== 2.0.2
|
|
|
|
Low | December 31, 2005 12/31/05 |
== 1.0.2
== 1.1.1
== 1.1.2
== 1.0.1
== 2.0
== 1.1.4
== 1.1.0
== 1.1.3
== 1.1.5
|
|
|
|
Medium | May 2, 2005 5/2/05 |
== 1.0.2
== 1.1.1
== 1.1.2
== 1.0.1
== 1.1.4
== 1.1.0
== 1.1.3
|
|
|
|
Low | October 20, 2004 10/20/04 |
== 1.1.2
|
|
|
|
Medium | December 31, 2002 12/31/02 |
== 1.0.1
|
apache / openoffice
59 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
Medium | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
Medium | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
High | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
High | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
High | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
Low | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
High | November 12, 2025 11/12/25 |
< 4.1.16
|
|
|
|
High | December 29, 2023 12/29/23 |
< 4.1.15
|
|
|
|
High | March 24, 2023 3/24/23 |
< 4.1.14
|
|
|
|
High | March 24, 2023 3/24/23 |
<= 4.1.13
|
|
|
|
High | August 15, 2022 8/15/22 |
< 4.1.13
|
|
|
|
High | August 15, 2022 8/15/22 |
< 4.1.13
|
|
|
|
High | October 11, 2021 10/11/21 |
< 4.1.11
|
|
|
|
High | October 11, 2021 10/11/21 |
< 4.1.11
|
|
|
|
Medium | October 11, 2021 10/11/21 |
< 4.1.11
|
|
|
|
Medium | October 7, 2021 10/7/21 |
<= 4.1.10
|
|
|
|
High | October 7, 2021 10/7/21 |
== 4.1.8
|
|
|
|
High | September 23, 2021 9/23/21 |
<= 4.1.10
|
|
|
|
High | April 15, 2021 4/15/21 |
<= 4.1.8
|
|
|
|
High | November 17, 2020 11/17/20 |
>= 4.0.0 < 4.1.8
|
|
|
|
High | November 27, 2019 11/27/19 |
== 3.3.0
|
|
|
|
Low | January 31, 2019 1/31/19 |
<= 4.1.5
|
|
|
|
Medium | May 1, 2018 5/1/18 |
== 4.1.5
|
|
|
|
High | November 20, 2017 11/20/17 |
< 4.1.4
|
|
|
|
Low | November 20, 2017 11/20/17 |
<= 4.1.3
|
|
|
|
High | November 20, 2017 11/20/17 |
< 4.1.4
|
|
|
|
High | November 20, 2017 11/20/17 |
< 4.1.4
|
|
|
|
High | November 20, 2017 11/20/17 |
< 4.1.3
|
|
|
|
High | November 13, 2017 11/13/17 |
<= 4.1.2
|
|
|
|
Medium | August 5, 2016 8/5/16 |
<= 4.1.2
|
|
|
|
Medium | November 10, 2015 11/10/15 |
<= 4.1.1
|
|
|
|
Medium | November 10, 2015 11/10/15 |
<= 4.1.1
|
|
|
|
Medium | November 10, 2015 11/10/15 |
<= 4.1.1
|
|
|
|
Low | November 10, 2015 11/10/15 |
<= 4.1.1
|
|
|
|
Medium | April 28, 2015 4/28/15 |
<= 4.1.1
|
|
|
|
Low | August 27, 2014 8/27/14 |
< 4.1.1
|
|
|
|
High | August 26, 2014 8/26/14 |
< 4.1.1
|
|
|
|
Medium | July 31, 2013 7/31/13 |
< 4.0.0
|
|
|
|
Medium | July 31, 2013 7/31/13 |
< 4.0.0
|
|
|
|
High | August 6, 2012 8/6/12 |
< 3.4.1
|
|
|
|
Medium | June 17, 2012 6/17/12 |
== 3.3.0
== 3.4.0-beta
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
Medium | January 28, 2011 1/28/11 |
>= 3.0.0 < 3.3.0
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
High | January 28, 2011 1/28/11 |
>= 2.0.0 < 3.3.0
|
|
|
|
High | December 7, 2010 12/7/10 |
>= 3.0.0 < 3.3.0
>= 2.1.0 <= 2.4.3
|
Showing vulnerabilities for 2 products matching "openoffice". Each product has independent pagination.
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.