How severe is CVE-2012-0528?

CVE-2012-0528 has a CVSS 2.0 base score of 5.8, rated medium severity.

Is CVE-2012-0528 being actively exploited?

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

What products are affected by CVE-2012-0528?

CVE-2012-0528 primarily affects Oracle Database Server. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2012-0528?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2012-0528 published?

CVE-2012-0528 was published on 2012-05-03 and last updated on 2026-06-16.

CVE-2012-0528

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

Key facts

Severity: Medium (CVSS 2.0 base score 5.8)
EPSS exploit prediction: 2% (77th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Database Server
Published: 2012-05-03
Last modified: 2026-06-16

Description

Unspecified vulnerability in the Enterprise Manager Base Platform component in Oracle Database Server 10.2.0.3, 10.2.0.4, 10.2.0.5, and 11.1.0.7, and Oracle Enterprise Manager Grid Control, allows remote attackers to affect confidentiality and integrity via unknown vectors related to Security Framework.

Frequently asked questions

What is CVE-2012-0528?: Unspecified vulnerability in the Enterprise Manager Base Platform component in Oracle Database Server 10.2.0.3, 10.2.0.4, 10.2.0.5, and 11.1.0.7, and Oracle Enterprise Manager Grid Control, allows remote attackers to affect confidentiality and integrity via unknown vectors related to Security Framework.
How severe is CVE-2012-0528?: CVE-2012-0528 has a CVSS 2.0 base score of 5.8, rated medium severity.
Is CVE-2012-0528 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (77th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-0528?: CVE-2012-0528 primarily affects Oracle Database Server. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-0528?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-0528 published?: CVE-2012-0528 was published on 2012-05-03 and last updated on 2026-06-16.

References

Affected products (5)

cpe:2.3:a:oracle:database_server:10.2.0.3:*:*:*:*:*:*:*
cpe:2.3:a:oracle:database_server:10.2.0.4:*:*:*:*:*:*:*
cpe:2.3:a:oracle:database_server:10.2.0.5:*:*:*:*:*:*:*
cpe:2.3:a:oracle:database_server:11.1.0.7:*:*:*:*:*:*:*
cpe:2.3:a:oracle:enterprise_manager_grid_control:*:*:*:*:*:*:*:*

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 →