Welcome Guest. | Log In | Register | Membership Benefits

Nasdaq Says Web-Facing Application Was Compromised

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

Feb 07, 2011 | 10:30 PM | 

By Tim Wilson

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.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS












Featured Webcasts
Featured Whitepapers
Featured Reports
Bugs
ENTERPRISE VULNERABILITIES
Vulnerability:ssl-vpn end-point interrogator/installer activex control
Published:2010-11-03
Severity:High
Description:Stack-based buffer overflow in SonicWALL SSL-VPN End-Point Interrogator/Installer ActiveX control (Aventail.EPInstaller) before 10.5.2 and 10.0.5 hotfix 3 allows remote attackers to execute arbitrary code via long (1) CabURL and (2) Location arguments to the Install3rdPartyComponent method.
Vulnerability:gvim
Published:2010-11-03
Severity:High
Description:Untrusted search path vulnerability in VIM Development Group GVim before 7.3.034, and possibly other versions before 7.3.46, allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse User32.dll or other DLL that is located in the same folder as a .TXT file. NOTE: some of these details are obtained from third party information.
Vulnerability:cforms
Published:2010-11-03
Severity:Medium
Description:Multiple cross-site scripting (XSS) vulnerabilities in wp-content/plugins/cforms/lib_ajax.php in cforms WordPress plugin 11.5 allow remote attackers to inject arbitrary web script or HTML via the (1) rs and (2) rsargs[] parameters.
Vulnerability:links, wsn links, wsn links
Published:2010-11-03
Severity:High
Description:Multiple SQL injection vulnerabilities in search.php in WSN Links 5.0.x before 5.0.81, 5.1.x before 5.1.51, and 6.0.x before 6.0.1 allow remote attackers to execute arbitrary SQL commands via the (1) namecondition or (2) namesearch parameter.
Vulnerability:deluxebb
Published:2010-11-03
Severity:Medium
Description:SQL injection vulnerability in misc.php in DeluxeBB 1.3, and possibly earlier, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the xthedateformat parameter in a register action, a different vector than CVE-2005-2989, CVE-2006-2503, and CVE-2009-1033.



Briefing Centers
POWERFUL INFORMATION
AT YOUR FINGERTIPS
(SPONSORED LINKS)