CVE-2016-0472
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 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 confidenceUnspecified vulnerability in Oracle XDB (XML Database) component affecting versions 11.2.0.4, 12.1.0.1, and 12.1.0.2. Exploitable by remote authenticated users, impacting confidentiality and availability through unknown vectors in the XDB subsystem.
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
- None
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:N/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.
-
Determine Oracle Database versionConnect to the database as SYSDBA and run: SELECT VERSION FROM V$INSTANCE; or use lsnrctl status to check the database version from the listenerAffected if The version displayed is exactly 11.2.0.4, 12.1.0.1, or 12.1.0.2
-
Confirm XDB component is installedQuery the Oracle dictionary: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE 'Oracle XML Database%';Affected if XDB is present in the registry with status VALID, indicating the component is installed and operational
-
Verify XDB HTTP listener is enabledCheck listener.ora for XDB HTTP service on port 8080, or run lsnrctl status and look for service 'XDB' on port 8080 or similarAffected if The XDB HTTP listener is configured and the service is in LISTENER.ORA or showing as LISTENING status
-
Verify XDB FTP listener is enabledCheck listener.ora for XDB FTP service on port 2100, or examine network configuration for FTP listenerAffected if The XDB FTP listener is configured and listening on port 2100
You are affected if your Oracle Database version is exactly 11.2.0.4, 12.1.0.1, or 12.1.0.2 AND the XDB component is installed with either the HTTP or FTP listener enabled, allowing remote authenticated access to XDB.
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) for January 2016 or later. If XDB is not required, consider disabling the XDB HTTP and FTP listeners, and restrict network access to the database to limit exposure to authenticated attackers.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0472 — 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-2016-0472 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