dbcve.org
E Business SuiteApplication · Oracle

CVE-2016-0456

MEDIUM · 5.0 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 →
59/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 Application Mgmt Pack for E-Business Suite component in Oracle E-Business Suite 12.1 and 12.2 allows remote attackers to affect confidentiality via vectors related to REST Framework, a different vulnerability than CVE-2016-0457. NOTE: the previous information is from the January 2016 CPU. Oracle has not commented on third-party claims that this issue is an XML External Entity (XXE) vulnerability, which allows remote attackers to read arbitrary files, cause a denial of service, conduct server-side request forgery (SSRF) attacks, or conduct SMB Relay attacks via a crafted DTD in an XML request to OA_HTML/copxmllcmservicecontroller.js.

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

This is a vulnerability in Oracle E-Business Suite 12.1/12.2's Application Mgmt Pack REST Framework (OA_HTML/copxmllcmservicecontroller.js). Third-party researchers identified it as an XML External Entity (XXE) flaw where crafted DTD in XML requests allows remote attackers to read arbitrary files from the server (confidentiality impact), conduct SSRF, cause denial of service, or perform SMB Relay attacks.

MitigationApply Oracle's January 2016 Critical Patch Update (CPU) for E-Business Suite. Additionally, disable external entity processing in XML parsers and implement strict input validation on the affected endpoint.

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
E Business SuiteApplication
Affected:= 12.1= 12.2

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 version
    Log into Oracle E-Business Suite and navigate to the About Oracle Applications page (usually via Help > About Oracle Applications menu), or query the FND_PRODUCT_GROUPS table using SQL. Alternatively, check the INSTALL_TOP/oraInst.loc file for the version string.
    Affected if The installed version is exactly 12.1 or exactly 12.2 (these are the only affected versions per CVE-2016-0456)
  2. Verify affected component file exists
    Check for the presence of copxmllcmservicecontroller.js in the OA_HTML directory of the E-Business Suite web tier. The typical path is $OA_HTML/copxmllcmservicecontroller.js or under the web application root.
    Affected if The file copxmllcmservicecontroller.js exists in the OA_HTML directory, indicating the vulnerable Application Mgmt Pack REST Framework component is installed
  3. Confirm endpoint is accessible
    Attempt to access the URL pattern OA_HTML/copxmllcmservicecontroller.js or the REST endpoint it serves (typically under /OA_HTML/copxmllcmservice/ or similar paths). Use a browser or curl to test if the endpoint responds.
    Affected if The endpoint responds to HTTP/HTTPS requests, meaning it is exposed and potentially exploitable
  4. Check XML parser configuration for external entity processing
    Review XML parser settings or configuration files used by the Application Mgmt Pack REST Framework. Look for settings related to DTD processing, external entity resolution, or XXE protection in the application server configuration (e.g., Oracle WebLogic or Oracle Application Server config).
    Affected if External entity processing is enabled in XML parsers and no input validation is performed on the XML endpoint

You are affected if you run Oracle E-Business Suite version 12.1 or 12.2 AND the copxmllcmservicecontroller.js component is installed and accessible, with XML external entity processing enabled on the endpoint.

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's January 2016 Critical Patch Update (CPU) for E-Business Suite. Additionally, disable external entity processing in XML parsers and implement strict input validation on the affected endpoint.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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