Modernizing Authentication — What It Takes to Transform Secure Access
Oracle's October Critical Patch Update (CPU) addresses 51 vulnerabilities spread across the company's product portfolio, a marked improvement over last October's update. The quarterly release also introduces an update to the system it uses to score the severity of vulnerabilities.
Oracle's namesake database products, which have 27 disclosed vulnerabilities, get the majority of the 51 fixes. According to Oracle's advisory, seven of the database vulnerabilities may be remotely exploitable without authentication.
Oracle Application Server gets 11 fixes, seven of which are remotely exploitable without authentication. There are eight security fixes for the Oracle E-Business Suite and one is remotely exploitable without authentication. Oracle Collaboration Suite gets seven fixes. Oracle PeopleSoft Enterprise PeopleTools gets two security fixes, and one new security fix for PeopleSoft Enterprise Human Capital Management.
This year's update also includes version 2 of the Common Vulnerability Scoring System (CVSS), which provides a benchmarking base metric system in order to score the relative severity of a reported vulnerability. The company adopted the system last year to expand its security information disclosure method.
"It is worthwhile to reiterate again that CVSS provides a standard-based approach for assessing the criticality of vulnerabilities," Eric Maurice, manager for security in Oracle's global technology business unit, wrote on Oracle's security blog.
"In other words, CVSS assists customers to understand the significance of a given vulnerability in their environment, and assess the priority that should be given to patching that specific vulnerability against production requirements."
With CVSS 2.0, he continued, a number of changes have been introduced that make the standard more representative of real-world vulnerabilities.
But while the new version of CVSS has more parameters, Amichai Shulman, CTO of application data security company Imperva, said that the scores have remained the same.
"Based on our analysis, we recommend that security officers take a close look at the details composing the risk score rather than accepting the score itself," Shulman wrote in an e-mail sent to InternetNews.com.
"For example, the highest-ranked vulnerability is only 6.5 out of 10, yet it is easy to exploit remotely and allows the attacker to take complete control of the database. This is a serious vulnerability, but its score does not reflect that fact."