Oracle JavaVM Database Takeover
A new vulnerability discovered in the Oracle Database JavaVM component can result in complete database compromise and shell access to the underlying server.
Antecedentes
Oracle released an out-of-band update to its flagship database product for an authenticated vulnerability in the JavaVM component. According to Oracle, the vulnerability "can result in complete compromise of the Oracle Database and shell access to the underlying server." The same issue was found and patched in the July 2018 critical patch update (CPU) but was not reported as a critical vulnerability for unspecified reasons.
Vulnerability details
According to Oracle, this vulnerability affects “...versions 11.2.0.4 and 12.2.0.1 on Windows. CVE-2018-3110 has a CVSS v3 base score of 9.9, and can result in complete compromise of the Oracle Database and shell access to the underlying server. CVE-2018-3110 also affects Oracle Database version 12.1.0.2 on Windows as well as Oracle Database on Linux and Unix, however patches for those versions and platforms were included in the July 2018 CPU.”
This vulnerability affects Windows Oracle databases via the “Oracle Net” protocol and requires a user with “Create Session” privileges for the JavaVM component. No credit was provided in the advisory and, as is often the case with many Oracle vulnerabilities, exploitation details are sparse.
Nota: While CVE-2018-3004 from the July CPU appears to be related, as the same component is affected, Oracle has clarified that these CVEs are unrelated and the fix for CVE-2018-3110 was silently included in the July CPU for a subset of their product line in an effort to protect their customers.
Impact assessment
Because database authentication is required to exploit this vulnerability, the impact is lessened. However, the potential for complete database takeover means anyone with an Oracle database in their environment should take remediation steps immediately. In addition, enterprises running versions of Oracle DB which were patched for the July CPU are already protected.
Urgently required actions
If your business uses an Oracle database, we recommend updating immediately based on Oracle’s guidance
Tenable.io Vulnerability Management, Tenable.io Container Security, SecurityCenter and Nessus detect this vulnerability. Below is a list of plugins Tenable has released to determine if the Oracle databases in your environment are affected. Tenable will continue to monitor the situation and provide updated protection as required.
|
Plugin ID |
Nombre |
Description |
|
oracle_rdbms_cpu_jul_2018.nasl |
July 2018 Oracle DB CPU |
|
|
oracle_rdbms_cve_2018_3110.nasl |
August 2018 Oracle DB check for CVE-2018-3110 |
Para obtener más información
Learn more about Tenable.io, the first Cyber Exposure platform for holistic management of your modern attack surface. Get a free 60-day trial of Tenable.io Vulnerability Management.
Artículos relacionados
Tenable Cloud Security Study Reveals a Whopping 95% of Surveyed Organizations Suffered a Cloud-Related Breach Over an 18-Month Period
May 14, 2024The finding from the Tenable 2024 Cloud Security Outlook study is a clear sign of the need for proactive and robust cloud security. Read on to learn more about the study’s findings, including the main challenges cloud security teams face, their strategies for better protecting their cloud infrastructure and the tools they use to measure success.
Shifting the Paradigm: Why the Cyber Insurance Industry Should Focus on Preventive Security
May 13, 2024As claims and losses climb, it’s clear that preventive security should be prioritized more when designing a cyber insurance policy. Here’s why preventive security investments are cost effective and can lead to lower premiums.
Cybersecurity Snapshot: New Guide Explains How To Assess if Software Is Secure by Design, While NIST Publishes GenAI Risk Framework
May 10, 2024Is the software your company wants to buy securely designed? A new guide outlines how you can find out. Meanwhile, a new NIST framework can help you assess your GenAI systems’ risks. Plus, a survey shows a big disconnect between AI usage (high) and AI governance (low). And MITRE’s breach post-mortem brims with insights and actionable tips. And much more!
