dbcve.org
E Business SuiteApplication · Oracle

CVE-2016-0457

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-0456. 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/lcmServiceController.jsp.

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 · high confidence

This is an XML External Entity (XXE) vulnerability in Oracle E-Business Suite's Application Management Pack REST Framework (lcmServiceController.jsp). Attackers can exploit this by sending crafted XML with malicious DTD to read arbitrary files from the server filesystem, cause denial of service, perform SSRF attacks, or execute SMB Relay attacks.

MitigationApply Oracle Critical Patch Update (January 2016) to address this vulnerability. As a compensating control, disable or restrict unauthenticated access to OA_HTML/lcmServiceController.jsp and implement strict XML input validation/parsing with XXE protection enabled.

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. Identify Oracle E-Business Suite version
    Query the database using 'SELECT product_version FROM fnd_product_versions WHERE product_name LIKE "%E-Business Suite%";' or run the version check script provided by Oracle (AD_IDENTIFICATION), or check the $APPL_TOP/../OracleEBS-app.xml manifest file
    Affected if The installed version is 12.1 or 12.2
  2. Locate the vulnerable JSP file
    Search for the file lcmServiceController.jsp in the OA_HTML directory (typically $OA_HTML/lcmServiceController.jsp or <IAS_INSTANCE>/OA_HTML/lcmServiceController.jsp). Use 'find $OA_HTML -name lcmServiceController.jsp' on the application tier
    Affected if The file lcmServiceController.jsp exists in the OA_HTML directory
  3. Verify accessibility of the vulnerable endpoint
    Attempt an HTTP GET request to http(s)://<hostname>:<port>/OA_HTML/lcmServiceController.jsp from an untrusted network or unauthenticated context. If the JSP responds (even with an error page) rather than rejecting the request, the endpoint is exposed
    Affected if The endpoint returns any response without requiring authentication (no login session, no OAM gate, no IP restriction)
  4. Check XML parser security configuration
    Review the Java XML parser configuration for the EBS application. Inspect the application server (WebLogic/OC4J) XML processor settings. Look for whether external entity parsing is explicitly disabled. Check if the application uses a hardened XMLInputFactory with features like XMLConstants.ACCESS_EXTERNAL_DTD and XMLConstants.ACCESS_EXTERNAL_SCHEMA set to restrict
    Affected if The XML parser has XXE protections disabled, or the application lacks explicit configuration to block external entity resolution

A system is affected if it runs Oracle E-Business Suite 12.1 or 12.2, has lcmServiceController.jsp accessible without authentication, and the XML parser does not have XXE protections explicitly enabled.

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 Update (January 2016) to address this vulnerability. As a compensating control, disable or restrict unauthenticated access to OA_HTML/lcmServiceController.jsp and implement strict XML input validation/parsing with XXE protection enabled.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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