Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] Oracle WebLogic Server weblogic.corba.utils.MarshallObject Java Deserialization Remote Code Execution

Critical

Synopsis

While testing a prior vulnerability (CVE-2016-0638) for writing a detection plugin, Tenable noticed that Oracle's class filter blacklist hadn't changed. Another WebLogic bypass object (weblogic.corba.utils.MarshallObject) had been published on GitHub. Tenable tested to see if that had been patched via the April 19, 2016 patches as well, and it appears that is not the case. As such, an unauthenticated attacker can still achieve remote code execution using a known blacklist bypass. Tenable generated an exploit that popped calc.exe against a patched WebLogic Server 12.1.3 as a demonstration and provided it to Oracle.

Solution

Oracle has released a patch for this issue as part of the July 19, 2016 CPU.

Disclosure Timeline

2016-04-21 - Issue discovered
2016-04-28 - Vendor informed via secalert_us@oracle.com
2016-05-02 - Oracle files security bug, tracked as S0730407
2016-05-24 - Oracle automated status sent: "Issue fixed in main codeline, scheduled for a future CPU"
2016-06-24 - Oracle automated status sent: "Issue fixed in main codeline, scheduled for a future CPU"
2016-07-15 - Oracle automated status sent: "fixed in the upcoming Critical Patch Update, due .. July 19, 2016."
2016-07-15 - Tenable asks for the CVE assignment for this issue.
2016-07-19 - Oracle releases July CPU fixing the issue.
2016-07-19 - Tenable asks for the CVE assignment for this issue, again.
2016-07-19 - Oracle provides CVE assignment
2016-07-20 - Tenable confirms this vulnerability is fixed

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email advisories@tenable.com