CVE-2012-3132
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 · uneditedSQL injection vulnerability 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 execute arbitrary SQL commands via vectors involving CREATE INDEX with a CTXSYS.CONTEXT INDEXTYPE and DBMS_STATS.GATHER_TABLE_STATS.
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 · high confidenceSQL injection vulnerability in Oracle Database Server allows remote authenticated users to execute arbitrary SQL commands via CREATE INDEX statements using CTXSYS.CONTEXT INDEXTYPE combined with DBMS_STATS.GATHER_TABLE_STATS. The vulnerability affects versions 10.2.0.3 through 11.2.0.3 and requires Oracle authentication but permits full SQL execution.
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.7= 11.2.0.2= 11.2.0.3CVSS 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
- Partial
AV:N/AC:L/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Database Server versionConnect to the database as a privileged user (e.g., SYS or SYSTEM) and run: SELECT VERSION FROM V$INSTANCE;Affected if The version returned is 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, or 11.2.0.3
-
Verify CTXSYS schema exists and is accessibleRun: SELECT USERNAME FROM DBA_USERS WHERE USERNAME = 'CTXSYS';Affected if The CTXSYS user account exists and is not locked or expired, enabling the vulnerable CONTEXT INDEXTYPE functionality
-
Check for active CONTEXT indexesRun: SELECT OWNER, INDEX_NAME, INDEX_TYPE FROM DBA_INDEXES WHERE INDEX_TYPE = 'CONTEXT';Affected if Any CONTEXT index type is present, indicating the vulnerable feature is in use
-
Audit for CREATE INDEX with DBMS_STATS callsReview database audit logs or unified audit for CREATE INDEX statements referencing CTXSYS.CONTEXT combined with DBMS_ST.GATHER_TABLE_STATS or GATHER_INDEX_STATSAffected if Such patterns are found in audit logs, indicating the vulnerability was potentially exploited
You are affected if your Oracle Database Server version is 10.2.0.3 through 11.2.0.3 and the CTXSYS schema with CONTEXT index functionality is accessible to authenticated 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 Updates (CPU) for CVE-2012-3132. Restrict database authentication and audit privileged accounts to limit exposure until patches can be deployed.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3132 — 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-3132 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