dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2012-0552

HIGH · 9.0 CVSS v2.0 Published 2012-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unspecified vulnerability in the Oracle Spatial component in Oracle Database Server 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, and 11.2.0.3 allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unspecified vulnerability in Oracle Spatial component allows remote authenticated users to affect confidentiality, integrity, and availability. Oracle Spatial handles geospatial and location data within Oracle Database; the vulnerability enables complete compromise via unknown vectors.

MitigationApply Oracle Critical Patch Update (CPU) for April 2012 which addresses CVE-2012-0552. Restrict Oracle Database access to authorized users and minimize the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Database ServerDatabase / datastore
Affected:= 10.2.0.3= 10.2.0.4= 10.2.0.5= 11.1.0.7= 11.2.0.2= 11.2.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Database version
    Query the database using SELECT * FROM v$version; or check the Oracle inventory files on the server. Compare the reported version against the affected list: 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, 11.2.0.3.
    Affected if The installed version matches one of the listed affected versions.
  2. Confirm Oracle Spatial component is present
    Query the database using SELECT comp_name, status FROM dba_registry WHERE comp_name LIKE '%Spatial%'; or check if spatial indexes and MDSYS schema objects exist.
    Affected if Oracle Spatial is installed and enabled in the database.
  3. Verify remote network access is enabled
    Check the Oracle Listener configuration (listener.ora) and whether the database is exposed on network listeners. Verify with lsnrctl status or by reviewing listener.ora settings.
    Affected if The Oracle Listener is running and accepting remote connections.
  4. Identify authenticated user access
    Review which database users have CREATE SESSION privilege and can connect remotely. Check DBA_ROLE_PRIVS for users with DBA privileges, especially those granted to application schemas.
    Affected if Remote authenticated users (beyond local OS-authenticated users) can connect to the database.

The environment is affected if the installed Oracle Database version is one of the affected versions (10.2.0.3-10.2.0.5, 11.1.0.7, 11.2.0.2, or 11.2.0.3), Oracle Spatial component is installed, and the database accepts remote authenticated connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for April 2012 which addresses CVE-2012-0552. Restrict Oracle Database access to authorized users and minimize the attack surface.

Recommended fix High confidence

Oracle Database 11.2.0.4 or later (12c/19c/21c)

  1. 1. Identify the current Oracle Database Server version using: SELECT VERSION FROM V$INSTANCE;
  2. 2. Confirm the Oracle Spatial component is in use: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Spatial%';
  3. 3. Schedule a maintenance window for the database upgrade
  4. 4. For Oracle Database 10.2.0.x: Upgrade to 11.2.0.4 or higher (12c/19c/21c) following Oracle's upgrade documentation
  5. 5. For Oracle Database 11.1.0.7: Upgrade to 11.2.0.4 or higher (12c/19c/21c) following Oracle's upgrade documentation
  6. 6. Apply the latest Oracle Critical Patch Update (CPU) after upgrade to ensure all security patches are applied
  7. 7. Verify the upgrade was successful by checking: SELECT VERSION FROM V$INSTANCE;
  8. 8. Test application functionality with Oracle Spatial features
Caveat Oracle major version upgrades may require application compatibility testing; refer to Oracle's Upgrade Guide for deprecated features and required migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Database Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,048.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0552 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data