Flaw (CVE-2018-3110) in the Java VM component of Oracle’s Database Server is easily exploitable, security experts warn.
Oracle this week urged organizations to immediately patch a critical vulnerability in multiple versions of Oracle database that gives attackers a way to completely compromise the technology and gain root access to the underlying server.
The flaw [CVE-2018-3110] exists in the Java VM component of Oracle’s Database Server and affects versions 184.108.40.206 and 220.127.116.11 on Windows. It also impacts Oracle Database version 18.104.22.168 on Windows and Oracle Database on Linux and Unix. However, patches for these particular versions of the database were issued with Oracle’s July 2018 monthly patch update.
In an out-of-band security advisory Monday, the enterprise software giant described the vulnerability as an issue that can be remotely exploited only by fully authenticated users who are able to create a session with the database. Even so, it urged customers to take immediate action to address the issue. “Due to the nature of this vulnerability, Oracle strongly recommends that customers take action without delay,” the advisory noted.
The National Vulnerability Database categorized the threat as easily exploitable. “[It] allows low privileged attacker having Create Session privilege with network access via Oracle Net to compromise Java VM.”
While the flaw exists in the Java VM component, an attacker can exploit the vulnerability to attack other technologies as well. “Successful attacks of this vulnerability can result in takeover of Java VM,” the NVD cautioned.
Oracle, like other major security vendors, typically releases security patches and updates on a fixed, publicly available schedule. While companies like Microsoft follow a monthly schedule, Oracle releases its patch updates in a quarterly cycle— in January, April, July, and October. Because of the complexities involved in applying patches to running databases, even that pace is often too hard to keep up with for many organizations.
“Organizations can take ages,” to apply patches, even if they are as critical as the one announced this week, says John Matthew Holt, founder and chief technology officer at Waratek. “Oracle themselves claim that their average customer runs nearly a year beyond in applying critical patches. Other third-party software testing vendors claim that 86% of even the most serious flaws take more than 30 days to fix.”
What makes those numbers especially troubling is the fact that attackers using automated scanners can identify and launch attacks against just announced vulnerabilities within hours of disclosure, Holt says.
With this particular vulnerability though, delay would be inadvisable. Organizations need to realize that vulnerabilities don’t get any easier to exploit, he says. “When someone pushes an exploit script into the wild, any two-penny script kiddie will be able to take hostage one of the most popular and widespread database systems in-use by companies and governments in a single click,” Holt notes.
For most organizations, the principal risk group for this particular vulnerability is internal actors such as rogue employees. External attackers who have compromised lateral systems in an internal corporate network are another major risk group, Holt says.
“A simple static script will be all that is required,” he predicts. “As soon as one is released, then anyone can wield this vulnerability in a single click.”