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.

Perimeter

6/8/2009
02:12 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

Hacking Challenge Shows XSS Still King

Last week, another company got egg on its face by running a "we're-so-secure-you-can't-hack-our-stuff contest." When are companies going to learn claims like that always backfire?

Last week, another company got egg on its face by running a "we're-so-secure-you-can't-hack-our-stuff contest." When are companies going to learn claims like that always backfire?The latest "victim" is StrongWebMail, a company that said its Webmail solution was unhackable because it required two-factor authentication using the customer's phone. Of course, it was wrong. It published details of a contest that said it would award $10,000 to the person who successfully hacked into the Webmail of the company's CEO and retrieved the details of a task that was due on June 26. Mike Bailey, Lance James, and Aviv Raff stepped up and delivered the required information, which was then confirmed by the CEO.

Several different sources are currently reporting that the exploit was carried out through cross site scripting (XSS), but the company has yet to confirm the details, and the possible winners are not allowed to disclose their methods. (See PC World and Skeptikal.org for more information.)

Do PR stunts like this one make sense when trying to get your company's name or new product out there? How does someone sell the rest of the company after putting a sign on your own back that reads, "HACK ME!"? Especially to the legal team?

There's a saying that bad publicity is better than no publicity, and maybe that's what StrongWebMail is banking on here since the authentication mechanism isn't what was exploited. Exploiting an XSS vulnerability is an exploitation of the Website itself, the Web browser, and user behavior of either opening the e-mail or clicking on the link from an attacker. It was not a compromise of two-factor authentication. That said, does it matter? Not if the attacker can get to the data. Who cares how he got to it?

Maybe StrongWebMail's intentions were not so much PR. As I mentioned, it wanted to tout the greatness of its two-factor authentication and how it couldn't be circumvented. That in itself is putting a target on its back for any hacker and security researcher to take a whack at them. It's the kind of challenge, and money, that will bring all levels of hackers out of the woodwork. With a reward of $10,000, this challenge had to be one of the cheapest pen-tests ever, considering how much manpower was probably focused on it.

Whatever its goal, XSS has again proved to be more than a simple parlor trick for causing pop-up messages on affected sites. And just because you have multifactor authentication, encryption, and more, social engineering a user into opening an e-mail or clicking on a link is quite effective at bypassing all of those layers.

When are they going to learn?

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/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-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.
CVE-2019-20897
PUBLISHED: 2020-07-13
The avatar upload feature in affected versions of Atlassian Jira Server and Data Center allows remote attackers to achieve Denial of Service via a crafted PNG file. The affected versions are before version 8.5.4, from version 8.6.0 before 8.6.2, and from version 8.7.0 before 8.7.1.
CVE-2020-15105
PUBLISHED: 2020-07-10
Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authenticati...