CVE-2015-4900
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.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality, integrity, and availability 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 confidenceCVE-2015-4900 is an unspecified vulnerability in Oracle Database Server's XDB (XML Database) component affecting versions 11.2.0.4, 12.1.0.1, and 12.1.0.2. The vulnerability allows remote authenticated users to impact confidentiality, integrity, and availability through unknown vectors related to XDB processing.
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.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
- 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 versionConnect to the database as SYSDBA and run: SELECT VERSION FROM V$INSTANCE; or check the Oracle inventory for installed database versions.Affected if The version returned matches 11.2.0.4, 12.1.0.1, or 12.1.0.2 exactly.
-
Verify XDB component is installedConnect as SYSDBA and run: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%XDB%';Affected if XDB shows as VALID and installed in the database registry.
-
Check if XDB HTTP listener is enabledQuery: SELECT DBMS_XDB.GETHTTPORT() FROM DUAL; to check the HTTP port, and verify if the XDB HTTP service is configured and accessible.Affected if A port number is returned (typically 8080) indicating XDB HTTP is enabled and potentially exposed.
-
Verify XDB repository access configurationCheck if XDB repository is accessible by attempting to access DBMS_XDB or querying XDB-related objects. Run: SELECT COUNT(*) FROM DBA_OBJECTS WHERE OBJECT_NAME LIKE '%XDB%';Affected if XDB objects are present and accessible to authenticated database users.
The environment is affected if the installed Oracle Database version is exactly 11.2.0.4, 12.1.0.1, or 12.1.0.2 AND the XDB component is installed and enabled, allowing remote authenticated users to access XDB functionality.
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) patches for October 2015 or upgrade to a patched version of Oracle Database Server. Restrict XDB access and follow the principle of least privilege for database accounts.
- 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-4900 — 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-4900 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