A penetration testing company uncovered security vulnerabilities on the NASDAQ website that remained open for two weeks after the stock exchange was notified.
The vulnerabilities were uncovered by Geneva-based High Tech Bridge, and have now been patched.
“I initially reported one XSS [cross-site scripting] and one open redirect, which I found in about 10 minutes,” High-Tech Bridge CEO Ilia Kolochenko told SecurityWeek in an email. “I didn’t want to dig further without their permission as it would be unethical, but I am pretty sure they have other vulnerabilities, probably even more dangerous than XSS.”
Cross-site scripting allows attackers to inject client-side script into Web pages, and is one of the most common vulnerabilities on the Web. If exploited, the vulnerabilities could have had a number of implications for anyone who visited the NASDAQ site, including the theft of browser cookies and phishing attacks where users are tricked into giving up personal details by what appear to be legitimate requests from Nasdaq.
Criticizing NASDAQ for its response, Kolochenko said he contacted NASDAQ about the issue Sept. 2 but never heard back, and added that the issues were not patched until the incident received media coverage Sept. 16.
“They were notified on the 2nd of September 2013 by an email sent to a dozen of addresses found on their website, as well as to some “generic” emails like security@ and abuse@,” he said. “What is actually surprising is that they don’t have a contact to “Report website issue”, not even speaking about “Report security bug”. Hopefully, now they will become more open now.”
The incident is unrelated to a software glitch and other technical problems that caused a three-hour outage in late August that temporarily halted trading. In an interview with SecurityWeek, a NASDAQ spokesperson said that all matters related to security are taken very seriously by Nasdaq.
“We work with leading security vendors, and have a trained and professional team that evaluates all credible threats across all of our digital assets,” he said.
To prevent cross-site scripting vulnerabilities, the Open Web Application Security Project (OWASP) recommends developers properly escape all untrusted data based on the HTML context the data will be placed into.
“Strict source code review policy should be applied to any script that is publicly accessible. Security should become an essential part of SDLC,” said Kolochenko. “Today many web developers simply forget about application security being focused mainly on productivity, compatibility, SEO, SMO, etc.”