CVE-2011-2301
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 Oracle Text component in Oracle Database Server 10.1.0.5, 10.2.0.3, 10.2.0.4, and 11.1.0.7 allows remote authenticated users to affect confidentiality, integrity, and availability, related to CTXSYS.DRVDISP.
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 Text component (CTXSYS.DRVDISP) affecting Oracle Database Server versions 10.1.0.5 through 11.1.0.7. Exploitable by remote authenticated users with potential for complete compromise of confidentiality, integrity, and availability.
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.1.0.5= 10.2.0.3= 10.2.0.4= 11.1.0.7CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Check Oracle Database server versionQuery the database with: SELECT VERSION FROM PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle Database%'; Or check the Oracle inventory or registry tables.Affected if Version matches 10.1.0.5, 10.2.0.3, 10.2.0.4, or 11.1.0.7 exactly (these are the affected versions listed)
-
Verify Oracle Text component is installedQuery: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Text%';Affected if Oracle Text component shows as INSTALLED and VALID - the vulnerability only applies when this component is present and enabled
-
Confirm CTXSYS account statusQuery: SELECT USERNAME, ACCOUNT_STATUS FROM DBA_USERS WHERE USERNAME = 'CTXSYS';Affected if CTXSYS account exists and is OPEN/UNLOCKED - this is the vulnerable component that can be exploited by authenticated users
-
Check for remote authentication exposureReview database listener configuration and network access controls. Check if database allows remote connections from untrusted networks.Affected if Database is accessible remotely to users outside the trusted network, especially if CTXSYS account can be authenticated to remotely (e.g., via SQL*Net)
-
Check CTXSYS account privilegesQuery: SELECT GRANTED_ROLE, PRIVILEGE FROM DBA_ROLE_PRIVS JOIN DBA_SYS_PRIVS ON(GRANTED_ROLE=PRIVILEGE) WHERE GRANTEE='CTXSYS' UNION SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS WHERE GRANTEE='CTXSYS';Affected if CTXSYS account has elevated privileges beyond what is required for normal Oracle Text operation - combined with remote access, this enables the full compromise vector
Environment is affected if running Oracle Database version 10.1.0.5, 10.2.0.3, 10.2.0.4, or 11.1.0.7 AND the Oracle Text component (CTXSYS) is installed and accessible to remote 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 Update patches for CVE-2011-2301. Consider restricting CTXSYS account privileges and network access until patching can be completed.
- 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-2011-2301 — 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-2011-2301 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