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.

Risk

6/20/2008
12:31 AM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Mozilla Confirms TippingPoint's Cheap Shot (Whoops. I Meant Vulnerability Announcement)

Mozilla security chief Window Snyder says that there is, in fact, a security flaw in the foundation's just-released Firefox 3.0 Web browser. Her announcement confirms the sucker-punch swung by TippingPoint Technologies just hours after Firefox's release.

Mozilla security chief Window Snyder says that there is, in fact, a security flaw in the foundation's just-released Firefox 3.0 Web browser. Her announcement confirms the sucker-punch swung by TippingPoint Technologies just hours after Firefox's release.Within hours of the GA (general availability) release of Firefox 3.0, an anonymous researcher sold vulnerability information to TippingPoint's Zero Day Initiative (ZDI). In ZDI, TippingPoint pays for the vulnerability data. While not many details have been been released about the flaw, ZDI's alert came with an extra splash of hype surrounding the vulnerability:

We verified the vulnerability in our lab, acquired it from the researcher, then promptly reported the vulnerability to the Mozilla security team shortly after. Successful exploitation of the vulnerability could allow an attacker to execute arbitrary code. Not unlike most browser-based vulnerabilities that we see these days, user interaction is required, such as clicking on a link in e-mail or visiting a malicious web page.

Here's how the flaw was described to me in an e-mail sent by TippingPoint's PR firm, publicizing their find, closely timed with the blog post, and soliciting interviews about their ZDI program:

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code, permitting the attacker to completely take over the vulnerable process, potentially allowing the machine running the process to be completely controlled by the attacker. TippingPoint researchers continue to see these types of "user-interaction required" browser-based vulnerabilities -- such as clicking on a link in email or inadvertently visiting a malicious web page.

I'm not about to disconnect from the Internet, or uninstall my copy of Firefox 3.0, just yet. First, in order to exploit the flaw, users would have to be enticed to click on a link, or end up at a bad guy's Web site. So the flaw isn't "worm-able," and would primarily only be a problem to those users who individually fell victim. (Granted, there's too many who don't watch their URLs, but the flaw requiring user interaction mitigates widespread risk.) Bottom line is that there's no Internet-virus pandemic on the horizon, and no real need to sound the alarm.

Second, the timing of the announcement is highly, very highly, suspect. From the ZDI blog:

What we can confirm is that about five hours after the official release of Firefox 3.0 on June 17th, our Zero Day Initiative program received a critical vulnerability affecting Firefox 3.0 as well as prior versions of Firefox 2.0.x.

So, within five hours of Firefox 3.0's release someone found and confirmed the flaw? Why wasn't the flaw found in any of the earlier release candidates? The flaw also resided in previous 2.0.x versions of Firefox. Sure, it's possible that no one found the flaw in the earlier versions, and researchers missed this flaw in the release candidates that have been available for months and months.

Common sense begs the more likely scenario:

Chances are that the flaw was discovered at an earlier date, and the researcher sandbagged the release to TippingPoint to coincide with 3.0's big download day. Can't say I blame the researcher for that, could be a nice way to ensure successful sale of the vulnerability. But TippingPoint's announcing the zero-day flaw before the patch is released is nothing more than this vendor's typical publicity grab.

Much better for us all if security vendors acted responsibly and quietly informed the software maker of the flaw, and only publish the fact that these vulnerabilities exist if the software vendor has been dragging their feet.

And there's been no sign of that in this case, just TippingPoint seeking some cheap PR.

Mozilla's update is available here.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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 Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17505
PUBLISHED: 2020-08-12
Artica Web Proxy 4.30.000000 allows an authenticated remote attacker to inject commands via the service-cmds parameter in cyrus.php. These commands are executed with root privileges via service_cmds_peform.
CVE-2020-17506
PUBLISHED: 2020-08-12
Artica Web Proxy 4.30.00000000 allows remote attacker to bypass privilege detection and gain web backend administrator privileges through SQL injection of the apikey parameter in fw.login.php.
CVE-2020-2035
PUBLISHED: 2020-08-12
When SSL/TLS Forward Proxy Decryption mode has been configured to decrypt the web transactions, the PAN-OS URL filtering feature inspects the HTTP Host and URL path headers for policy enforcement on the decrypted HTTPS web transactions but does not consider Server Name Indication (SNI) field within ...
CVE-2020-5415
PUBLISHED: 2020-08-12
Concourse, versions prior to 6.3.1 and 6.4.1, in installations which use the GitLab auth connector, is vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another user who is granted access to a Concourse team. GitLab groups do not have this vulnerabilit...
CVE-2020-6653
PUBLISHED: 2020-08-12
Eaton's Secure connect mobile app v1.7.3 & prior stores the user login credentials in logcat file when user create or register the account on the Mobile app. A malicious app or unauthorized user can harvest the information and later on can use the information to monitor and control the user's ac...