CVE-2016-0560
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 Customer Intelligence component in Oracle E-Business Suite 11.5.10.2, 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, and 12.2.5 allows remote attackers to affect confidentiality and integrity via unknown vectors, a different vulnerability than CVE-2016-0545, CVE-2016-0551, CVE-2016-0552, and CVE-2016-0559.
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 · high confidenceThis is an unspecified vulnerability in Oracle Customer Intelligence, a component of Oracle E-Business Suite affecting versions 11.5.10.2 through 12.2.5. The vulnerability allows remote attackers to impact confidentiality and integrity via unknown attack vectors. The CVSS 6.4 score indicates significant risk given the E-Business Suite handles sensitive business data.
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.5.10.2= 12.1.1= 12.1.2= 12.1.3= 12.2.3= 12.2.4= 12.2.5CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Confirm Oracle E-Business Suite installationRun SQL query SELECT version FROM apps.fnd_product_groups; or check the Oracle Applications Manager (OAM) interface for installed products.Affected if Oracle E-Business Suite is not installed - not affected.
-
Determine E-Business Suite release versionExecute SQL: SELECT release_name FROM fnd_product_groups; or query ad_bugs table: SELECT bug_number FROM ad_bugs WHERE bug_number IN ('20355665', '20355666');Affected if Version is NOT in the list 11.5.10.2, 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5 - not affected.
-
Verify Oracle Customer Intelligence module is enabledQuery ICX Catlog tables or check via Oracle Applications Manager: Responsibility: System Administrator > Oracle Applications Manager > Module Mapping > verify 'Customer Intelligence' product is installed and enabled.Affected if Customer Intelligence module is not present or not enabled - not affected.
-
Check for January 2016 CPU patch appliedRun: SELECT patch_name, creation_date FROM ad_bugs WHERE patch_name LIKE '%2035566%' OR patch_name LIKE '%CPUJAN2016%'; or check opatch lsinventory for patch 20355665/20355666.Affected if CPU Jan 2016 patch is NOT applied - environment may be affected if versions match.
Environment is affected if Oracle E-Business Suite version falls within 11.5.10.2 through 12.2.5 AND the Customer Intelligence module is enabled AND the January 2016 CPU patch is not applied.
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 (CPU) for January 2016 which addresses this vulnerability. Before production deployment, test thoroughly in a non-production environment to ensure patch compatibility with existing customizations and integrations.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0560 — 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-0560 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