CVE-2012-0528
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 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.
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 confidenceUnspecified vulnerability in Oracle Enterprise Manager Base Platform's Security Framework affecting versions 10.2.0.3 through 10.2.0.5, 11.1.0.7, and Grid Control. Allows remote attackers to impact confidentiality and integrity via unknown vectors.
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= 10.2.0.3= 10.2.0.4= 10.2.0.5= 11.1.0.7all versionsCVSS 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
- None
AV:N/AC:M/Au:N/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.
-
Identify Oracle Enterprise Manager installationLook for Oracle Enterprise Manager directories such as $ORACLE_HOME/oms, /opt/oracle/oms, or check for 'Grid Control' or 'Enterprise Manager' processes running (such as emctl, emagent). On Windows, check Services for 'Oracle Enterprise Manager' or check Program Files for Oracle folders.Affected if Oracle Enterprise Manager Grid Control or Base Platform is installed and running
-
Determine Enterprise Manager versionRun 'emctl status agent' or 'emctl status oms' from the bin directory, or check the Oracle inventory (oralnventory) for Enterprise Manager components. Also check $ORACLE_HOME/oms/sysman/install/History.xml or similar version files.Affected if Version matches 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, or any version of Grid Control prior to the April 2012 CPU
-
Verify Security Framework component is presentCheck if the Security Framework module is configured in Enterprise Manager by examining $ORACLE_HOME/oms/install directory or accessing Enterprise Manager console. Look for security-related configurations under the Enterprise Manager admin console.Affected if Security Framework component is enabled or configured in the Enterprise Manager environment
-
Check for legacy Grid Control installationsReview all Oracle installations for Grid Control (distinct from Database Control). Grid Control was a separate product used to manage multiple databases. Check for /opt/oracle/gridcontrol, /u01/app/oracle/gridcontrol, or similar paths. Look for emagent and oms processes.Affected if Grid Control (as opposed to Database Control) is installed, regardless of version
If Oracle Enterprise Manager Grid Control of any version, or Base Platform versions 10.2.0.3-10.2.0.5 or 11.1.0.7 is installed with Security Framework enabled, the environment is affected by this vulnerability.
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 (CPU) for April 2012 or upgrade to a supported Oracle Database and Enterprise Manager version. If running legacy systems, consider migration to Oracle Enterprise Manager 13c or later.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0528 — 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-0528 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