Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

7 Ways Oracle Hurts Database Customers' Security

Oracle's missteps during the TNS Poison disclosure debacle highlight its ongoing failures in helping customers secure their databases.

Last week Oracle bumped heads with the database security community in a communications blunder that caused a proof of concept to be released for an unpatched four-year-old vulnerability in the database's TNS Listener service. This week Oracle released a workaround, but still no patch, reigniting critics' claims that the company is neglecting its database customers with shoddy patching practices.

Security professionals believe that Oracle is hurting its database customers through security negligence. Here are their charges. Dark Reading did try to contact Oracle for this article, but the company did not respond to inquiries.

1. Failing to play nice with researchers
According to security researcher Joxean Koret, the events that unfolded around the TNS Poison vulnerability are emblematic of Oracle's relationship with the research community and its customers. The drama started when the company credited Koret for a hand in its Critical Patch Update and told him in a separate email exchange that it had fixed a vulnerability he disclosed to the company in 2008.

"Oracle said the vulnerability was fixed. I decided to publish details about the vulnerability, fully believing it was fixed; so far, so good," Koret told Dark Reading. "Then it turned out the vulnerability wasn't fixed at all and there was no patch because, they said: 'the vulnerability was fixed in later versions.'"

In other words, Oracle did not release a patch for the vulnerability but instead only fixed the issue in code destined for future releases of its database products.

Koret believes that Oracle willfully misled him and the rest of its customer base in order to improve its statistics on closing out unresolved vulnerabilities disclosed by outside researchers.

"Probably, they decided to say that vulnerabilities are fixed even when there is no available patch because of the bad reputation they have fixing vulnerabilities. This way, they can say they fixed a vulnerability in a shorter time," says Koret, who called the situation a tragicomedy.

Regardless of intentions, the incident wasn't Oracle's finest moment, says database security guru Alexander Kornbrust, who agrees that Oracle dropped the ball on this one.

Read the rest of this article on Dark Reading.

Think your corporate website isn't vulnerable to a SQL injection attack? Start rethinking. SQL injection is among the most prevalent--and most dangerous--techniques for exploiting Web applications and attacking back-end databases that house critical business information at companies of every size. In our Stop SQL Injection report, we explain how SQL injection works and how to secure your Web apps and databases against it. (Free registration required.)

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/13/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Mobile App Fraud Jumped in Q1 as Attackers Pivot from Browsers
Jai Vijayan, Contributing Writer,  7/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14174
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to view titles of a private project via an Insecure Direct Object References (IDOR) vulnerability in the Administration Permission Helper. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5....
CVE-2019-20901
PUBLISHED: 2020-07-13
The login.jsp resource in Jira before version 8.5.2, and from version 8.6.0 before version 8.6.1 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect in the os_destination parameter.
CVE-2019-20898
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.
CVE-2019-20899
PUBLISHED: 2020-07-13
The Gadget API in Atlassian Jira Server and Data Center in affected versions allows remote attackers to make Jira unresponsive via repeated requests to a certain endpoint in the Gadget API. The affected versions are before version 8.5.4, and from version 8.6.0 before 8.6.1.
CVE-2019-20900
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the Add Field module. The affected versions are before version 8.7.0.