# Oracle E-Business Suite and Java Security: What You Need to Know

- URL: https://www.integrigy.com/security-resources/oracle-e-business-suite-and-java-security-what-you-need-know
- Published: 2019-03-27
- Type: Webinar
- Products: Oracle E-Business Suite
- Focus areas: Vulnerabilities, Oracle Critical Patch Updates
- Applies to: EBS 12.0, EBS 12.1, EBS 12.2
- PDF: https://www.integrigy.com/sites/default/files/Integrigy%20-%20Oracle%20EBS%20and%20Java%20Security%20What%20You%20Need%20to%20Know.pdf
- Recording: https://www.youtube.com/watch?v=dSh7Fd23IbE

> Webinar on the Java installations in Oracle E-Business Suite, on the servers and on end-user desktops, how Java vulnerabilities fixed in each quarterly Critical Patch Update can be used to attack each tier, and how to protect each installation.

Oracle E-Business Suite (EBS) runs on Java, on the server and in the Forms interface, with multiple Java installations on the application and database servers and on end-user desktops. These installations are often not upgraded, or cannot be upgraded, to the latest Java version, while each quarterly Critical Patch Update fixes Java security bugs, such as Java deserialization, by a version upgrade rather than a patch.

We review where EBS uses Java, how Java vulnerabilities can be used to attack each EBS tier, and how to protect each installation. DBAs and IT security can then find every Java installation in their EBS environment and decide how to update or protect it.

## Key Points

- Running `find . -executable -type f -name java` on a single-node EBS 12.2.7 Vision install finds 29 `java` executables across both 12.2 file systems and the database home, and EBS also runs Java in the database JVM, the OEM and Audit Vault agents and the client's Java Plugin or Java Web Start.
- As of March 2019, Java 6 server support had ended in December 2018 and Java 7 had server support through July 2022, Java 8 had no EBS server support but client support through March 2025, and Java 9 to 12 had no EBS support (Doc ID 418664.1); all of those dates have since passed.
- Java vulnerabilities reach EBS through six attack vectors (the client-side Plugin or Web Start, untrusted code, untrusted data, Java deserialization, cryptographic issues and local access), and the application server's web tier JVM (10.1.3 in 12.1) and the database JavaVM are open to both untrusted data and deserialization attacks, which need a vulnerable helper class such as Apache Struts.
- On desktops, use Java Web Start, which needs JRE 8 Update 181 for multiple Forms sessions, rather than the Java Plugin, which Firefox, Chrome and MS Edge have desupported (MOS Note 2188898.1 covers the switch), update it each quarter for the CPU, and verify that every Jinitiator installation is removed from all desktops.
- On the application server, upgrade the 12.2 web tier JDK (`FMW_HOME/webtier/jdk`) every quarter with only minimal testing of basic self-service functions, upgrade the 10.1.2 home's JDK whenever you upgrade Oracle Forms (MOS Note 1530033.1 for 12.2, 1467892.1 for 12.1), and upgrade the web server's Java for TLS 1.2 and the strongest ciphers (MOS Note ID 1367293.1 for 12.2).
- In the database, any account can potentially run Java classes in the database JVM, some exploits need only `CREATE SESSION`, and the fixes come in the database CPU (SPU/PSU) with mandatory additional steps, while Oracle does not support upgrading the Oracle Home JDK (MOS Note 1449674.1) and the OPatch, OEM Agent and Audit Vault Agent JDKs are always multiple versions behind.
