Oracle issues workarounds for zero-day hole

Powered by SC Magazine
 

Company moves after public disclosure.

Oracle has acknowledged a still-unpatched database vulnerability after proof-of-concept code was published.

The company advised users to apply workaround measures and configuration changes.

The serious vulnerability earned a 7.5 CVSS score and was remotely exploitable without the need for authentication.

It affected 10g and the most current version 11g of Oracle Database.

Researcher Joxean Koret reported the man-in-the-middle flaw to bug-bounty program iSight Partners four years ago, which shared details with Oracle per its reward program specifications.

He disclosed the proof-of-concept code after he thought Oracle had fixed the flaw in a patch issued  two weeks ago and was given credit in the company's Security-In-Depth program.

But in an email exchange he discovered the defect was only repaired in future versions of the database.

He said attackers can exploit the flaw to "sniff any connection" made to the database without the need for credentials, and can also inject malicious commands.

He added that he is not aware of any in-the-wild attacks underway.

Oracle tried to fix vulnerabilities first in "the main code line" and then "backported" through its quarterly security updates.

But sometimes backporting is not possible due to heavy amounts of code required or because doing so will cause serious performance issues for customers.

This article originally appeared at scmagazineus.com

Copyright © SC Magazine, US edition


Oracle issues workarounds for zero-day hole
 
 
 
Top Stories
Westpac committed to core banking plan
[Blog post] Now with leadership.
 
The True Cost of BYOD - 2014 survey
Twelve months on from our first study, is BYOD a better proposition?
 
Photos: Unboxing the Magnus supercomputer
Pawsey's biggest beast slots into place.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  29%
 
Application integration concerns
  3%
 
Security and compliance concerns
  27%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  22%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1143

Vote