Customer IntelligenceApplication · Oracle

CVE-2016-0559

MEDIUM · 6.4 CVSS v2.0 Published 2016-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified 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-0560.

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 confidence

Unspecified vulnerability in Oracle Customer Intelligence component of Oracle E-Business Suite affecting versions 11.5.10.2 through 12.2.5. CVSS 6.4 indicates network-exploitable with low complexity, no authentication required, impacting confidentiality and integrity but not availability. The 'unspecified' nature means specific technical vectors (SQL injection, parameter tampering, etc.) are not disclosed in the advisory.

MitigationApply Oracle Critical Patch Updates (CPU) for January 2016 and subsequent updates. Given unspecified vectors, ensure all EBS patches are current and review Oracle's January 2016 CPU for specific fixes.

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
Customer IntelligenceApplication
Affected:= 11.5.10.2= 12.1.1= 12.1.2= 12.1.3= 12.2.3= 12.2.4= 12.2.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle E-Business Suite installation
    Check for Oracle E-Business Suite by locating the EBS environment file (ENV_FILE) or by querying the database for the Applications version using 'SELECT release_name FROM fnd_product_groups;'
    Affected if Oracle E-Business Suite is not present in the environment
  2. Determine the exact EBS version
    Run 'SELECT version FROM applsys.fnd_product_groups;' or check the $APPL_TOP/admin/$CONTEXT_NAME.xml file for the release version string
    Affected if The version falls within 11.5.10.2 through 12.2.5 (including 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5)
  3. Verify Customer Intelligence module is installed and enabled
    Query the database for the Customer Intelligence product status using 'SELECT product_version, status FROM fnd_product_installations WHERE product_id LIKE "%CIG%" OR product_id LIKE "%CUSTOMER%INTELLIGENCE%";'
    Affected if Customer Intelligence is installed and shows status as 'I' (Installed) or 'S' (Shared)
  4. Check for direct network exposure of EBS interfaces
    Review the Oracle E-Business Suite web entry points accessible from the network, specifically the /OA_HTML/CigHtml or /OA_HTML/ci/ paths if exposed, and verify if the EBS login page (/OA_HTML/AppsLogin) is internet-facing without proper access controls
    Affected if The EBS web interfaces are exposed to untrusted networks without authentication gates

The environment is affected if Oracle E-Business Suite with Customer Intelligence module is installed and the version falls within 11.5.10.2 through 12.2.5, with web interfaces network-accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates (CPU) for January 2016 and subsequent updates. Given unspecified vectors, ensure all EBS patches are current and review Oracle's January 2016 CPU for specific fixes.

Fix this in Customer Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0559 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-0559 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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