CVE-2010-0860
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 Core RDBMS component in Oracle Database 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.4, and 11.1.0.7 allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors related to the Create User privilege.
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 confidenceOracle Database Core RDBMS vulnerability allowing remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors related to Create User privilege. The unspecified nature of the attack vector and the high CVSS score (7.1) indicate a significant privilege escalation or abuse risk in database user management.
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= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 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
- High
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/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.
-
Determine Oracle Database server versionConnect to the database as a privileged user (like SYS or SYSTEM) and run: SELECT VERSION FROM V$INSTANCE; or check the registry$history table for patch history.Affected if The installed version matches one of the affected versions: 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.4, or 11.1.0.7.
-
Identify users granted CREATE USER system privilegeExecute: SELECT GRANTEE, PRIVILEGE, ADMIN_OPTION FROM DBA_SYS_PRIVS WHERE PRIVILEGE = 'CREATE USER'; to list all users, roles, or profiles that can create database users.Affected if Any user or role other than highly privileged administrative accounts (like SYS, SYSTEM) has the CREATE USER privilege.
-
Review privilege assignment necessityFor each user identified with CREATE USER privilege, verify whether that privilege is required for their legitimate job function. Query: SELECT * FROM DBA_TAB_PRIVS WHERE GRANTEE = 'TARGET_USER'; to understand their other privileges.Affected if Users who do not require CREATE USER privilege for their role have been granted this powerful system privilege, creating an attack surface.
You are affected if your Oracle Database version is one of the listed affected versions AND untrusted or non-administrative users hold the CREATE USER system privilege.
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 for affected versions (9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.4, 11.1.0.7). Restrict Create User privilege to minimum required accounts following principle of least privilege until patch can be applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0860 — 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-2010-0860 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