Skip to main content

Webinar

Oracle E-Business Suite Web Security Vulnerabilities Examined

63 min recording

Applies to
  • EBS 11i
  • EBS 12.0
  • EBS 12.1
  • EBS 12.2
CVE IDs
  • CVE-2016-0545
  • CVE-2016-0507
  • CVE-2016-0525
  • CVE-2016-0553
  • CVE-2016-0541
  • CVE-2016-0532

Download PDF (969 KB)

Webinar examining the security of the Oracle E-Business Suite web application: the SQL injection, cross-site scripting and other web vulnerabilities among the 416 EBS security fixes from 2005 to April 2016, and how to protect against them.

Play the Recording: Oracle E-Business Suite Web Security Vulnerabilities Examined
The recording plays from YouTube (youtube-nocookie.com) once you start it.

Oracle E-Business Suite is a large and complex web application that must be properly secured against web attacks from inside and outside the organization. Of the 416 EBS security vulnerabilities Oracle fixed between January 2005 and April 2016, about 120 were SQL injection bugs in web pages, which run an attacker's SQL as the APPS database account and can lead to a complete compromise of the application.

We examine EBS web security by analyzing and demonstrating these vulnerabilities, including two fixed in the January 2016 CPU, and discuss how to protect EBS from known vulnerabilities and common web application attacks. DBAs and security teams can then reduce their exposure with a proper DMZ configuration and virtual patching.

Key Points

  • EBS installs all 250+ modules and all web pages on every application server, and every page reaches the database as APPS: R12 has 8,000 JSP pages, 11,600 OA Framework pages and 4,000 forms, while 11i, long desupported, also exposes 850 modplsql database packages (removed in R12) on an Oracle Application Server 9iAS stack desupported around 2005.
  • SQL injection lets an attacker add SQL to a URL that EBS runs as APPS, as in a fnd_gfm.dispatch bug patched in Oracle Security Alert #32 that could change any application account's password, and CVE-2016-0545, which we demonstrate, lets an unauthenticated attacker run arbitrary SQL as APPS through the JSP page biccfgd2.jsp in 11.5.10.2 through 12.2.x.
  • Cross-site scripting (XSS) lets an attacker store JavaScript, for example in a job application's description field, that runs when an HR manager opens it and calls EBS URLs in a hidden frame, and CVE-2016-0507, which we demonstrate, is an XSS bug in an iReceivables modplsql database package in 11.5.10.2.
  • The January 2016 CPU also fixed SQL injection in a JSP page included in 70 Universal Work Queue (IEU) pages (CVE-2016-0525), arbitrary reads of application server files (CVE-2016-0553) and unauthenticated access to security authorizations (CVE-2016-0532), all blocked by the URL Firewall, and an XXE bug in a Configurator servlet (CVE-2016-0541) that the URL Firewall allows.
  • Deploying EBS in a DMZ requires every step of Oracle's DMZ note (380490.1 for R12, 287176.1 for the long-desupported 11i): the mandatory URL Firewall of Appendix E (url_fw.conf), a whitelist of allowed JSP pages and servlets, NODE_TRUST_LEVEL set to EXTERNAL (step 5.2), limited responsibilities (step 5.3), and only the modules Oracle certifies for a DMZ.
  • Virtual patching eliminates the risk of a security bug by blocking access to the vulnerable code, with your own web application firewall or EBS modsecurity rules or with our AppDefend, for which we analyze each Critical Patch Update and deliver predefined rules for all its web bugs.