How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, 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.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

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.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

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. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

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.

Q: How do we prioritize remediation without burning out the team?

Use a 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 so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

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.

328,411

Total vulnerabilities in the database

Vulnerabilities for products matching "ichitaro"

Found 3 matching products. Filters apply to all results.

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

justsystem / ichitaro

7 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2008-0223	High	January 10, 2008 1/10/08	== linux == 2007 == 11.0 == 2006 == 2005 == 12.0 == 13.0 == 2004
CVE-2007-6436	High	December 18, 2007 12/18/07	== 2007 == 2006 == 2005
CVE-2007-5687	High	October 28, 2007 10/28/07	== lite2 == linux == 11.0 == 2006 == 2005 == 12.0 == 13.0 == 2004
CVE-2007-4246	Medium	August 8, 2007 8/8/07	== 2007
CVE-2006-6400	Medium	December 10, 2006 12/10/06	* == 2006 == 2005
CVE-2006-5424	Medium	October 20, 2006 10/20/06	== 2006 == 2006_government_edition == 2006_trial_edition
CVE-2006-4326	High	August 24, 2006 8/24/06	== 9.0 == 10.0 == 11.0 == 2006 == 2005 == 12.0 == 13.0 == 2004

ichitaro / ichitaro

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2009-1054	High		March 24, 2009 3/24/09	== 13 == 2004 == 2005 == 2006 == 2007 == 2008 == lite2
CVE-2007-1938	Low		April 10, 2007 4/10/07	== 2006 == 2005 == 2007

justsystems / ichitaro

17 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2017-2789	High	February 24, 2017 2/24/17	*
CVE-2017-2790	High	February 24, 2017 2/24/17	*
CVE-2017-2791	Medium	February 24, 2017 2/24/17	== 2016
CVE-2014-7247	High	November 26, 2014 11/26/14	== 2010 == 2014 == 2012 == 2009 == 2008 == 6 == 7 == 2011 == 2013
CVE-2014-2003	High	June 16, 2014 6/16/14	== 2009 == 13 == 2012 == 2006 == 2011 <= 2014 == 2008 == 2005 == 10 == 12 == 2010 == 2013 == 2007 == 11 == 2004
CVE-2013-5990	High	November 13, 2013 11/13/13	== 2012 == 2013 == 2011 == 7 == 2006 == 2010 == 2007 == 2009 == 6 == 2008
CVE-2013-3644	High	June 18, 2013 6/18/13	== 7 == 2012 == 2006 == 2011 == 2013 == 2008 == 2010 == 2007 == 2009 == 6
CVE-2013-0707	High	March 1, 2013 3/1/13	== 2006 == 2007
CVE-2012-0269	High	April 27, 2012 4/27/12	== 2006 == 2011 == 2008 == 2010 == 2007 == 2009
CVE-2012-1242	Medium	April 27, 2012 4/27/12	== 2006 == 2011 == 2008 == 2010 == 2007 == 2009
CVE-2011-1331	High	July 18, 2011 7/18/11	== 2006 == 2011 == 2008 == 2005 == 2010 == 2007 == 2009 == 6
CVE-2010-3915	High	November 6, 2010 11/6/10	* == 2007 == 2009 == 2008
CVE-2010-3916	High	November 6, 2010 11/6/10	* == 2007 == 2009 == 2008
CVE-2010-2152	High	June 3, 2010 6/3/10	== 2008 == 2005 == 2007 == 2009 == 2006 == 2004
CVE-2010-1424	High	April 15, 2010 4/15/10	== 2009 == 2010 == 2006 == 2008 == 2007
CVE-2009-4737	High	April 6, 2010 4/6/10	== 2009 == 13 == 2006 == bungei == 2008 == 2005 == 2007 == 2004
CVE-2008-3919	High	September 4, 2008 9/4/08	*

Showing vulnerabilities for 3 products matching "ichitaro". 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

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

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.