CVE-2012-0512
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 · uneditedUnspecified vulnerability in the Enterprise Manager Base Platform component in Oracle Database Server 11.1.0.7 and 11.2.0.2 and Oracle Enterprise Manager Grid Control allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Enterprise Config Management.
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 confidenceCVE-2012-0512 is an unspecified vulnerability in Oracle Enterprise Manager Grid Control's Enterprise Config Management component affecting Database versions 11.1.0.7 and 11.2.0.2. The vulnerability allows remote authenticated users to compromise confidentiality and integrity via unknown vectors, but does not impact availability. The attack requires valid authentication credentials.
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= 11.1.0.7= 11.2.0.2CVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Oracle Database versionRun query: SELECT VERSION FROM V$INSTANCE; or check with Oracle inventory: opatch lsinventoryAffected if Version is exactly 11.1.0.7 or 11.2.0.2
-
Confirm Enterprise Manager Grid Control is deployedCheck if Oracle Enterprise Manager Grid Control is installed and running: look for EM GC processes, check Oracle inventory for 'Enterprise Manager Grid Control' component, or query: SELECT COMP_NAME, VERSION FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Enterprise Manager%';Affected if Enterprise Manager Grid Control with Enterprise Config Management component is present
-
Verify Enterprise Config Management component is enabledCheck if the Enterprise Config Management (ECM) component is configured: access Enterprise Manager console, go to 'Enterprise Config Management' link, or query repository for ECM targetsAffected if Enterprise Config Management targets exist in the Grid Control environment
-
Assess remote authentication exposureCheck if Oracle listeners allow remote connections and if database authentication is enabled. Review listener.ora for external connections, check SQLNET.AUTHENTICATION_SERVICES setting, and verify if Oracle EM is accessible over networkAffected if Remote network access to Oracle services is permitted and authentication is enabled
You are affected if you run Oracle Database 11.1.0.7 or 11.2.0.2 with Enterprise Manager Grid Control and its Enterprise Config Management component accessible to authenticated remote users
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update released in April 2012 or later. If the affected Oracle 11g versions are no longer supported, upgrade to a supported Oracle Database and Enterprise Manager version. Implement network segmentation and strict access controls to limit exposure to authenticated attackers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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