dbcve.org
Customer Interaction HistoryApplication · Oracle

CVE-2016-0529

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 Interaction History component in Oracle E-Business Suite 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 vectors related to User GUI, a different vulnerability than CVE-2016-0527, CVE-2016-0528, and CVE-2016-0530.

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

CVE-2016-0529 is an unspecified vulnerability in the Oracle Customer Interaction History component of Oracle E-Business Suite versions 12.1.1 through 12.2.5. The vulnerability allows remote attackers to impact confidentiality and integrity through the User GUI interface, likely via improper input handling or insufficient access controls in web-facing interfaces.

MitigationApply Oracle Critical Patch Updates (CPU) for Oracle E-Business Suite, specifically the January 2016 CPU which contains the fix for this vulnerability. Test thoroughly in a non-production environment before deploying to production systems.

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 Interaction HistoryApplication
Affected:= 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
    Query the database for E-Business Suite version information. Connect as APPS user and run: SELECT release_name FROM apps.fnd_product_groups; or check the context file $CONTEXT_FILE for the variable s_apps_version.
    Affected if The returned version matches any of: 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, or 12.2.5
  2. Confirm Customer Interaction History component is installed
    Query the database for installed Oracle modules: SELECT application_name, status FROM apps.fnd_application_vl WHERE application_name LIKE '%Customer Interaction%'; or check the modules installed via Oracle Applications Manager.
    Affected if The Customer Interaction History module shows status as 'I' (Installed) or 'S' (Shared); this indicates the vulnerable component is present in the environment.
  3. Verify web interface is accessible
    Check if Oracle E-Business Suite web listeners (Oracle HTTP Server / Apache) are running and the /OA_HTML/ directory is accessible. Use: ps -ef | grep -i httpd or check Oracle WebLogic/OHS status. Attempt to access the login page at the E-Business Suite URL.
    Affected if The web interface is reachable from network locations, particularly untrusted ones, making the GUI-based vulnerability exploitable.
  4. Check for Customer Interaction History responsibility
    Query for assigned responsibilities: SELECT responsibility_name FROM apps.fnd_responsibility_vl WHERE responsibility_name LIKE '%Customer Interaction%' OR responsibility_name LIKE '%Interaction History%';
    Affected if Users have assigned responsibilities that grant access to the Customer Interaction History function, enabling the attack vector through the User GUI interface.

You are affected if your Oracle E-Business Suite version is exactly 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, or 12.2.5 AND the Customer Interaction History component is installed AND users have access to it via the web GUI.

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 Oracle E-Business Suite, specifically the January 2016 CPU which contains the fix for this vulnerability. Test thoroughly in a non-production environment before deploying to production systems.

Fix this in Customer Interaction History 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-0529 — 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-0529 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