Vulnerability Database

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "officescan"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/officescan/1.2.3

trend_micro / officescan

29 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium January 21, 2009 1/21/09
== 8.0-sp1
High January 21, 2009 1/21/09
== 8.0-sp1
Low January 21, 2009 1/21/09
== 8.0-sp1
High October 23, 2008 10/23/08
== 8.0-sp1
== 7.3
Medium October 3, 2008 10/3/08
== 8.0-sp1_patch1
== 8.0-sp1
== 7.3
High October 3, 2008 10/3/08
== 8.0-sp1_patch1
== 8.0-sp1
Medium October 3, 2008 10/3/08
== 8.0-sp1_patch1
== 8.0-sp1
High September 16, 2008 9/16/08
== 7.3-patch_4
== 8.0
== 8.0-sp1
== 7.3
== 7.0
High July 30, 2008 7/30/08
== 7.3
High June 27, 2007 6/27/07
== 8.0
== 7.3
High June 27, 2007 6/27/07
== 8.0
High February 8, 2007 2/8/07
== 3.0
== 4.5.0
== 7.3
== corporate_3.0
== corporate_3.1.1
== corporate_3.11
== corporate_3.13
== corporate_3.5
== corporate_3.54
== corporate_5.02
== corporate_5.5
== corporate_5.58
== corporate_6.5
== corporate_7.0
== corporate_7.3
High December 11, 2006 12/11/06
== 7.3
High November 30, 2006 11/30/06
== 7.3
High November 30, 2006 11/30/06
== 7.3
Medium October 10, 2006 10/10/06
== corporate_6.5
== corporate_7.0
== 6.0
== corporate_7.3
Medium October 5, 2006 10/5/06
== corporate_7.3
High March 24, 2006 3/24/06
== 5.5
Medium October 30, 2005 10/30/05
== 7.0_engine_7.510.1002
High May 2, 2005 5/2/05
== corporate_6.5
== corporate_3.11
== corporate_3.0
== corporate_3.13
== corporate_5.02
== corporate_5.5
== 3.0
== corporate_3.1.1
== corporate_5.58
== corporate_3.5
== corporate_3.54
High December 31, 2004 12/31/04
== corporate_3.11
== corporate_5.02
== corporate_5.5
== corporate_3.13
== 3.0
== corporate_5.58
== corporate_3.5
== corporate_3.54
Low May 7, 2004 5/7/04
== corporate_3.11
== corporate_5.02
== corporate_3.13
== 3.0
== corporate_5.58
== corporate_3.5
== corporate_3.54
High December 31, 2003 12/31/03
== 3.11
== 3.5
== 3.0
== 3.1.1
== 3.13
== 3.54
Low December 18, 2002 12/18/02
== corporate_5.02
Medium October 15, 2001 10/15/01
== corporate_3.53
Medium August 22, 2001 8/22/01
== corporate_3.5
== corporate_3.54
Medium March 3, 2000 3/3/00
== 3.5
Medium February 28, 2000 2/28/00
== 3.5
Medium February 28, 2000 2/28/00
== 3.5

trendmicro / officescan

70 vulnerabilities found
Title Severity Exploit Date Affected Version
High August 4, 2021 8/4/21
== xg-sp1
High August 4, 2021 8/4/21
== xg-sp1
High July 29, 2021 7/29/21
== xg-sp1
High July 29, 2021 7/29/21
== xg-sp1
High April 13, 2021 4/13/21
== xg-sp1
High April 13, 2021 4/13/21
== xg-sp1
High April 13, 2021 4/13/21
== xg-sp1
Medium April 13, 2021 4/13/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
High February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium February 4, 2021 2/4/21
== xg-sp1
Medium December 1, 2020 12/1/20
== xg-sp1
Medium December 1, 2020 12/1/20
== xg-sp1
Medium December 1, 2020 12/1/20
== xg-sp1
Medium December 1, 2020 12/1/20
== xg-sp1
Medium December 1, 2020 12/1/20
== xg-sp1
High September 29, 2020 9/29/20
== xg-sp1
High September 1, 2020 9/1/20
== xg-sp1
Medium August 5, 2020 8/5/20
== xg-sp1
High March 18, 2020 3/18/20
== xg
== xg-sp1
High March 18, 2020 3/18/20
== xg
== xg-sp1
Critical March 18, 2020 3/18/20
== xg
== xg-sp1
Critical March 18, 2020 3/18/20
== xg
== xg-sp1
High March 18, 2020 3/18/20
== xg
== xg-sp1
High February 20, 2020 2/20/20
== xg
Low December 20, 2019 12/20/19
== xg
High October 28, 2019 10/28/19
== 11.0-sp1
== xg
== xg-sp1
Critical October 28, 2019 10/28/19
== 11.0-sp1
== xg
== xg-sp1
Low July 26, 2019 7/26/19
== 11.0-sp1
== xg
Medium April 5, 2019 4/5/19
== 11.0-sp1
== xg
== xg-sp1
Medium December 21, 2018 12/21/18
== xg
Medium December 21, 2018 12/21/18
== xg
High July 6, 2018 7/6/18
== 12.0
== 11.0
Low June 12, 2018 6/12/18
== 11.0-sp1
== xg
== xg-sp1
Medium June 12, 2018 6/12/18
== 11.0-sp1
== xg
== xg-sp1
Low June 12, 2018 6/12/18
== 11.0-sp1
== xg
== xg-sp1

Showing vulnerabilities for 2 products matching "officescan". Each product has independent pagination.

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.