CVE-2015-0455
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 XDB - XML Database component in Oracle Database Server 11.2.0.3, 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality via unknown vectors.
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 Database XDB (XML Database) component allows remote authenticated users to impact confidentiality. The attack requires valid database credentials and affects Oracle versions 11.2.0.3 through 12.1.0.2.
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.3= 11.2.0.4= 12.1.0.1= 12.1.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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:S/C:C/I:N/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 Database versionConnect to the database as a privileged user (e.g., SYS or SYSTEM) and execute: SELECT VERSION FROM V$INSTANCE; or check the oratab file /etc/oratab on the database server for the Oracle home entryAffected if Version matches 11.1.0.7, 11.2.0.3, 11.2.0.4, 12.1.0.1, or 12.1.0.2, or falls within the range 11.2.0.3 to 12.1.0.2
-
Verify XDB component is installedExecute: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%XDB%'; from a database connectionAffected if XDB is present in the registry with a status of VALID or LOADED
-
Confirm XDB protocol listeners are enabledCheck for XDB HTTP/WebDAV server: SELECT DBMS_XDB.GETHTTPPORT() FROM DUAL; Check for XDB FTP server: SELECT DBMS_XDB.GETFTPPORT() FROM DUAL; Also verify listener.ora for XDB service registrationAffected if HTTP or FTP ports are returned by these functions (non-zero values) indicating XDB listeners are active
-
Assess network accessibility to the databaseReview listener.ora and sqlnet.ora for allowed hosts/networks, and check if the database listener is exposed to untrusted networksAffected if Database listener accepts remote connections from hosts outside the trusted network
User is affected if running a vulnerable Oracle version (11.2.0.3-12.1.0.2 or specifically 11.1.0.7/11.2.0.4/12.1.0.1/12.1.0.2) with XDB component installed and accessible over the network, allowing a remote authenticated attacker to exploit the confidentiality flaw.
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) April 2015 or later. If immediate patching is not feasible, restrict network access to the database and disable XDB if not required.
- 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-2015-0455 — 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-2015-0455 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