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.


Nasdaq Says Web-Facing Application Was Compromised

Director's Desk infected with malware, but trading exchange unaffected, Nasdaq maintains

Nasdaq this weekend released a public disclosure that its Directors Desk application had been hacked, but it is emphasizing that its stock trading exchange was not affected.

"Through our normal security monitoring systems we detected suspicious files on the U.S. servers unrelated to our trading systems and determined that our Web-facing application, Directors Desk, was potentially affected, Nasdaq said in a statement. "The files were immediately removed and at this point, there is no evidence that any Directors Desk customer information was accessed or acquired by hackers. Our trading platform architecture operates independently from our Web-facing services like Directors Desk, and at no point was any of NASDAQ OMX's operated or serviced trading platforms compromised."

Although Nasdaq did not offer more detail on the breach, security experts around the Web were able to add some insight. In a blog posted Monday, researchers at anti-malware service provider Dasient dissected the attack and provided their feedback on what happened to Nasdaq.

"The target of this attack are the roughly 10,000 executives that use the Nasdaq information portal Directors Desk," Dasient said. "It appears that attackers were able to inject drive-by-download malware onto the website.

"Although sources familiar with the matter claim that the exchange's trading platforms were not affected, the risks of this attack are nonetheless very high. Visitors to the website would have been exposed to malware which could at a later time log their keystrokes and steal passwords to sensitive trading accounts or other information."

A source who is familiar with the Nasdaq security staffing situation said the organization has recently put a new security team in place, and inexperience might have been a factor in the breach. "Their security processes are immature and not well developed yet, being so new," said the source, who asked to remain anonymous. "From the inside, there are a lot of issues, and they are struggling to get their arms around everything."

Several vendors Monday said the hack could have been prevented.

"The real crime is that any organization can very well protect all data and mitigate the effect criminals can have fairly quickly and easily," commented Mark Bower, data security expert and VP product management at Voltage Security. "The focus should not have to be on compliance; it should be about doing the right thing and being responsible. If you have the ability to protect sensitive information but don't, that may very well boil down to criminal negligence."

"This breach demonstrates why organizations need better visibility into who and what is accessing their networks and their vital company data," said Frank Andrus, co-founder and CTO of network security vendor Bradford Networks. "Security starts with visibility."

"The Nasdaq security team apparently identified the issue internally, but the question is how long before the infection was detected," Dasient says in its blog. "How many days, weeks, or months was the infection out there? And how many users were exposed to the malware in the meantime?"

Nasdaq says it discovered the issue weeks before the breach disclosure, but did not go public at the request of law enforcement agencies that wanted to keep the investigation quiet.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.