dbcve.org
Customer IntelligenceApplication · Oracle

CVE-2016-0552

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-0559, 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

Vulnerability in the Oracle Customer Intelligence component of Oracle E-Business Suite allowing remote attackers to affect confidentiality and integrity via unspecified vectors. Distinct from related CVEs (CVE-2016-0545, CVE-2016-0551, CVE-2016-0559, CVE-2016-0560) affecting the same component.

MitigationApply the Oracle Critical Patch Update (January 2016) containing the fix for this vulnerability. Test thoroughly in a non-production environment before production deployment due to the complexity of Oracle E-Business Suite patches.

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 version
    Query the FND_PRODUCT_INSTALLATIONS table or use the Oracle AD Utilities (adident) to determine the installed E-Business Suite version. Connect as APPS user and run: SELECT product_version FROM fnd_product_installations WHERE product LIKE 'Oracle%';
    Affected if The displayed version matches any of: 11.5.10.2, 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, or 12.2.5
  2. Confirm Customer Intelligence component is installed
    Query the FND_APPLICATION or FND_PRODUCT_INSTALLATIONS tables to check if the Oracle Customer Intelligence module (often referenced as CSI - Customer Intelligence) is present in the installation. Run: SELECT application_name, application_id FROM fnd_application WHERE application_name LIKE '%CUSTOMER%INTELLIGENCE%' OR application_id IN (SELECT application_id FROM fnd_product_modules WHERE module_name LIKE '%CSI%');
    Affected if The Customer Intelligence module appears in the query results, confirming it is installed
  3. Check Customer Intelligence module version
    Query the specific version of the Customer Intelligence component by checking FND_PRODUCT_INSTALLATIONS for the exact CSI (Customer Intelligence) version entry: SELECT product_version, status FROM fnd_product_installations WHERE product LIKE '%Customer Intelligence%';
    Affected if The module version equals any of the affected versions listed in the CVE (11.5.10.2, 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, or 12.2.5)
  4. Verify Customer Intelligence is enabled and accessible
    Check if the Customer Intelligence responsibility is assigned to any active users and if the related web pages or forms are accessible. Query: SELECT DISTINCT responsibility_name FROM fnd_responsibility WHERE responsibility_name LIKE '%Customer Intelligence%'; Also check if the web entry point (typically under /OA_HTML/ci/) is reachable in the Oracle Applications web tier.
    Affected if The Customer Intelligence responsibility is active and accessible to users, meaning the vulnerability surface is exposed

You are affected if your Oracle E-Business Suite has Customer Intelligence installed and its version matches one of the affected versions (11.5.10.2, 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, or 12.2.5).

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 the Oracle Critical Patch Update (January 2016) containing the fix for this vulnerability. Test thoroughly in a non-production environment before production deployment due to the complexity of Oracle E-Business Suite patches.

Fix this in Customer Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-0552 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