dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2012-1737

MEDIUM · 6.8 CVSS v2.0 Published 2012-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges 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 Enterprise Manager for Oracle Database component in Oracle Database Server 11.1.0.7, 11.2.0.2, and 11.2.0.3, and Enterprise Manager Grid Control EM Base Platform 10.2.0.5, EM Base Platform 11.1.0.1, EM Plugin for DB 12.1.0.1, and EM Plugin for DB 12.1.0.2, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to DB Performance Advisories/UIs.

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 Enterprise Manager's Database Performance Advisories and UIs affecting Oracle Database Server 11.1.0.7, 11.2.0.2, 11.2.0.3, and multiple Enterprise Manager Grid Control versions. Allows remote attackers to impact confidentiality, integrity, and availability without authentication via unknown vectors in the performance advisory interfaces.

MitigationApply Oracle Critical Patch Update (CPU) April 2012 or later to address CVE-2012-1737. If patching is delayed, restrict network access to Enterprise Manager console interfaces to trusted networks only.

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:= 11.1.0.7= 11.2.0.2= 11.2.0.3
Enterprise Manager Grid ControlApplication
Affected:= 10.2.0.5= 11.1.0.1= 12.1.0.1= 12.1.0.2

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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. Confirm Oracle Enterprise Manager is installed
    Check for Enterprise Manager Grid Control processes (like emd, emagent) or examine installed Oracle software via 'opatch lsinventory' or Oracle inventory files in $ORACLE_HOME/../oraInventory
    Affected if Oracle Enterprise Manager Grid Control components are found on the system
  2. Identify Enterprise Manager Grid Control version
    Check the version of the Enterprise Manager installation: look for emctl status agent, emctl config agent getversion, or check the OMS (Oracle Management Service) version in the $ORACLE_HOME/sysman/install directory
    Affected if Version matches 10.2.0.5, 11.1.0.1, 12.1.0.1, or 12.1.0.2
  3. Identify connected Database Server versions
    Query the Oracle Database instances that Enterprise Manager monitors: use 'emctl status agent' to find agent targets, or check via Enterprise Manager console for monitored database versions
    Affected if Any monitored Oracle Database Server versions are 11.1.0.7, 11.2.0.2, or 11.2.0.3
  4. Verify Database Performance Advisories are accessible
    Check if the Database Performance Advisories feature is configured and accessible via Enterprise Manager console: attempt to access the Performance Advisories UI page (typically at /em/console/databasePerformance/advisors) or check EM repository for advisor target definitions
    Affected if Database Performance Advisories interface is available or configured in the Enterprise Manager environment
  5. Check network exposure of Enterprise Manager console
    Review firewall rules, load balancer configs, or Oracle HTTP Server settings to determine if Enterprise Manager console ports (typically 4889, 7788-7799, or HTTP/HTTPS ports) are accessible from untrusted networks
    Affected if Enterprise Manager console interfaces are exposed to networks outside trusted boundaries

A user is affected if they run any version of Oracle Enterprise Manager Grid Control matching 10.2.0.5, 11.1.0.1, 12.1.0.1, or 12.1.0.2, or monitor any Oracle Database Server 11.1.0.7, 11.2.0.2, or 11.2.0.3, with the Database Performance Advisories interface accessible over the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) April 2012 or later to address CVE-2012-1737. If patching is delayed, restrict network access to Enterprise Manager console interfaces to trusted networks only.

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1737 — 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-1737 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