How severe is CVE-2008-1818?

CVE-2008-1818 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2008-1818 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (86th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2008-1818?

CVE-2008-1818 affects Oracle Database Server. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2008-1818?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2008-1818 published?

CVE-2008-1818 was published on 2008-04-16 and last updated on 2026-06-16.

CVE-2008-1818

CVE-2008-1818 is a critical-severity vulnerability in Oracle Database Server with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 3% (86th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Database Server
Published: 2008-04-16
Last modified: 2026-06-16

Description

Unspecified vulnerability in the Authentication component in Oracle Database 11.1.0.6 has unknown impact and remote attack vectors, aka DB08.

Frequently asked questions

What is CVE-2008-1818?: Unspecified vulnerability in the Authentication component in Oracle Database 11.1.0.6 has unknown impact and remote attack vectors, aka DB08.
How severe is CVE-2008-1818?: CVE-2008-1818 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2008-1818 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (86th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-1818?: CVE-2008-1818 affects Oracle Database Server. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2008-1818?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2008-1818 published?: CVE-2008-1818 was published on 2008-04-16 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:oracle:database_server:11.1.0.6:*:*:*:*:*:*:*

More vulnerabilities in Oracle Database Server

CVE-2020-1953 — Critical (CVSS 10.0): Apache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation…
CVE-2015-4863 — Critical (CVSS 10.0): Unspecified vulnerability in the Portable Clusterware component in Oracle Database Server 11.2.0.4, 12.1.0.1, and…
CVE-2013-1534 — Critical (CVSS 10.0): Unspecified vulnerability in the Workload Manager component in Oracle Database Server 11.2.0.2 and 11.2.0.3, when used…
CVE-2010-0071 — Critical (CVSS 10.0): Unspecified vulnerability in the Listener component in Oracle Database 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.4, and…
CVE-2009-1992 — Critical (CVSS 10.0): Unspecified vulnerability in the Core RDBMS component in Oracle Database 9.2.0.8, 10.1.0.5, and 10.2.0.4 allows remote…
CVE-2009-1985 — Critical (CVSS 10.0): Unspecified vulnerability in the Network Authentication component in Oracle Database 9.2.0.8, 9.2.0.8DV, 10.1.0.5, and…

All CVEs affecting Oracle Database Server →