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.

326,895

Total vulnerabilities in the database

Vulnerabilities for products matching "oracle8i"

Found 1 matching product.

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

oracle / oracle8i

46 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2006-0552	High	February 4, 2006 2/4/06	== standard_8.1.7.4 == standard_8.0.6 == standard_8.0.6.3 == enterprise_8.1.7.4
CVE-2006-0262	High	January 18, 2006 1/18/06	== standard_8.1.7.4 == enterprise_8.1.7.4
CVE-2006-0271	High	January 18, 2006 1/18/06	== standard_8.1.7.4 == enterprise_8.1.7.4
CVE-2005-3641	High	November 16, 2005 11/16/05	== enterprise_8.0.5.0.0 == enterprise_8.0.6.0.0 == enterprise_8.0.6.0.1 == enterprise_8.1.5.0.0 == enterprise_8.1.5.0.2 == enterprise_8.1.5.1.0 == enterprise_8.1.6.0.0 == enterprise_8.1.6.1.0 == enterprise_8.1.7.0.0 == enterprise_8.1.7.1.0 == enterprise_8.1.7.4 == standard_8.0.6 == standard_8.0.6.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7.0.0 == standard_8.1.7.1 == standard_8.1.7.4
CVE-2004-0638	High	December 31, 2004 12/31/04	== standard_8.1.7.4 == enterprise_8.1.7.4
CVE-2004-0637	Medium	September 2, 2004 9/2/04	== standard_8.1.7_.4 == enterprise_8.1.7_.4
CVE-2004-1362	High	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1364	High	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1365	Low	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1366	Low	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1367	Low	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1368	High	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1369	Medium	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1370	High	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1371	High	August 4, 2004 8/4/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == enterprise_8.1.7_.4 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2004-1707	High	July 30, 2004 7/30/04	== enterprise_8.0.5_.0.0 == enterprise_8.0.6_.0.0 == enterprise_8.0.6_.0.1 == enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == standard_8.0.6 == standard_8.0.6_.3 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2003-0634	High	August 27, 2003 8/27/03	== enterprise_8.1.5_.0.0 == enterprise_8.1.5_.0.2 == enterprise_8.1.5_.1.0 == enterprise_8.1.6_.0.0 == enterprise_8.1.6_.1.0 == enterprise_8.1.7_.0.0 == enterprise_8.1.7_.1.0 == standard_8.1.5 == standard_8.1.6 == standard_8.1.7 == standard_8.1.7_.0.0 == standard_8.1.7_.1 == standard_8.1.7_.4
CVE-2003-0222	High	May 12, 2003 5/12/03	== 8.0x == 8.0.6 == 8.1.6 == 8.1.5 == 8.1.7 == 8.1.7.1 == 8.1.7.4 == 8.1x == 8.0.6.3
CVE-2003-0095	High	March 3, 2003 3/3/03	== 8.1.7.1 == 8.1.7
CVE-2003-0096	High	March 3, 2003 3/3/03	== 8.1.7.1 == 8.1.7
CVE-2002-1118	Medium	October 28, 2002 10/28/02	== 8.1.5.1.0_enterprise == 8.1.7.0.0_enterprise == 8.1.5.0.0_enterprise == 8.1.6 == 8.1.7.1 == 8.1.7 == 8.1.6.1.0_enterprise == 8.1.5 == 8.1.7.1.0_enterprise == 8.1.6.0.0_enterprise == 8.1.5.0.2_enterprise
CVE-2002-0840	Medium	October 11, 2002 10/11/02	== 8.1.7_.0.0_enterprise == 8.1.7.1 == 8.1.7 == 8.1.7_.1.0_enterprise
CVE-2002-0843	High	October 11, 2002 10/11/02	== 8.1.7.0.0_enterprise == 8.1.7.1 == 8.1.7 == 8.1.7.1.0_enterprise
CVE-2002-0857	High	September 5, 2002 9/5/02	== 8.1
CVE-2002-0858	High	September 5, 2002 9/5/02	*
CVE-2002-0559	High	July 3, 2002 7/3/02	== 8.1.7.1 == 8.1.7
CVE-2002-0560	Medium	July 3, 2002 7/3/02	== 8.1.7.1 == 8.1.7
CVE-2002-0561	High	July 3, 2002 7/3/02	== 8.1.7_.1 == 8.1.7
CVE-2002-0563	Medium	July 3, 2002 7/3/02	== 8.1.7_.1 == 8.1.7
CVE-2002-0564	High	July 3, 2002 7/3/02	== 8.1.7.1 == 8.1.7
CVE-2002-0566	Medium	July 3, 2002 7/3/02	== 8.1.7_.1 == 8.1.7
CVE-2002-0567	High	July 3, 2002 7/3/02	== 8.1.5 == 8.1.6 == 8.1.7 == 8.1.7.1 == enterprise_8.0.5.0.0 == enterprise_8.0.6.0.0 == enterprise_8.0.6.0.1 == enterprise_8.1.5.0.0 == enterprise_8.1.5.0.2 == enterprise_8.1.5.1.0 == enterprise_8.1.6.0.0 == enterprise_8.1.6.1.0 == enterprise_8.1.7.0.0 == enterprise_8.1.7.1.0
CVE-2002-0568	Low	July 3, 2002 7/3/02	== 8.1.7.1 == 8.1.7
CVE-2001-0498	Medium	July 21, 2001 7/21/01	<= 8.1.7
CVE-2001-0499	High	July 21, 2001 7/21/01	<= 8.1.7
CVE-2001-0515	Medium	July 21, 2001 7/21/01	== 8.1.6 <= 8.1.7
CVE-2001-0516	Medium	July 21, 2001 7/21/01	*
CVE-2001-0517	Medium	July 21, 2001 7/21/01	== 8.1.6 == 8.1.7
CVE-2001-0326	High	May 3, 2001 5/3/01	== 8.1.7_r3
CVE-2001-0126	High	March 12, 2001 3/12/01	== 8.1.7
CVE-2000-1180	Low	January 9, 2001 1/9/01	== 8.1.5
CVE-2000-0986	Low	December 19, 2000 12/19/00	== 8.1.5
CVE-2000-0987	Low	December 19, 2000 12/19/00	== 8.1.6
CVE-2000-0206	Medium	March 5, 2000 3/5/00	== 8.1.5
CVE-1999-0888	Low	August 16, 1999 8/16/99	== 8.0.4 == 8.0.5.1 == 8.0.3 == 8.0.5 == 8.1.5
CVE-1999-0711	Low	April 29, 1999 4/29/99	== 8.0.4 == 8.0.5.1 == 8.0.3 == 8.0.5 == 8.1.5

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.