dbcve.org
Customer IntelligenceApplication · Oracle

CVE-2016-0545

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-0551, CVE-2016-0552, 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

Unspecified vulnerability in Oracle E-Business Suite's Customer Intelligence component affecting versions 11.5.10.2 through 12.2.5. Allows remote attackers to impact confidentiality and integrity through unknown attack vectors. This is distinct from related CVEs (CVE-2016-0551, CVE-2016-0552, CVE-2016-0559, CVE-2016-0560) affecting the same component.

MitigationApply Oracle Critical Patch Updates (CPUs) for January 2016 and subsequent updates. Test thoroughly in non-production environment before production deployment due to Oracle E-Business Suite's complex interdependencies.

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. Confirm Oracle E-Business Suite installation
    Query the FND_INSTALLATION table: SELECT PRODUCT_VERSION FROM FND_INSTALLATION; This shows the version of Oracle Applications framework.
    Affected if Version matches 11.5.10.2, 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, or 12.2.5
  2. Verify Customer Intelligence component version
    Query the CRM_INFORMTN_ORG or check Oracle Application Manager (OAM) for installed component versions under the Customer Intelligence module.
    Affected if Customer Intelligence module version matches any of the affected versions listed above
  3. Check if Customer Intelligence is enabled
    Query the ICX_POR_CONFIGURATIONS table or access Oracle Application Manager to verify if the Customer Intelligence responsibility is assigned and active.
    Affected if Customer Intelligence responsibility is active and assigned to users
  4. Verify network exposure of the EBS interface
    Review Oracle E-Business Suite listener configuration (Oracle HTTP Server or Apache) and check if /OA_HTML/ or /OA_JSP/ paths are accessible externally.
    Affected if E-Business Suite web interfaces are reachable from untrusted networks without proper access controls
  5. Review audit logs for suspicious Customer Intelligence access
    Check ICX audit logs (ICX_AUDIT_TRAIL) and Oracle EBS access log files for unusual queries or data access patterns targeting customer data tables.
    Affected if Unexpected or unauthorized queries against customer-related tables are observed

A system is affected if it runs Oracle E-Business Suite version 11.5.10.2 through 12.2.5 with the Customer Intelligence component enabled and accessible, regardless of whether exploitation is observed.

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 (CPUs) for January 2016 and subsequent updates. Test thoroughly in non-production environment before production deployment due to Oracle E-Business Suite's complex interdependencies.

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-0545 — 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-0545 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