Welcome Guest. | Log In | Register | Membership Benefits

More Vendors Reacting Poorly To Disclosure

From Charlie Miller's latest attack on Apple's App Store to the outing of Carrier IQ, companies seem to be taking a step back and punishing researchers who disclose vulnerabilities

Dec 01, 2011 | 05:29 PM | 

By Robert Lemos, Contributing Editor
Dark Reading


Since 2008, security researcher Charlier Miller has scrutinized Apple products and found numerous vulnerabilities -- attention that the company has endured with equanimity, if not good grace. In early November, however, the tenuous relationship broke down.

Miller discovered a weakness in the iOS operating system that could allow a seemingly benign app to run malicious, unsigned code. The researcher decided to exploit the issue as well, building an application that passed Apple's checks to land in the App Store. Miller then made a video showing that he could take control of the phone without the user's knowledge.

"This is code that was not reviewed and could have done anything. It gets around the processes built into the App Store," he said in the video demonstration.

Apple's validation of applications headed to the App Store is a key component of the security of the iOS. The incident embarrassed the company, and Apple quickly took it out on Miller, banning him from the developer program -- and access to the App Store and developer resources -- for at least a year. Apple terminated the relationship because Miller broke his promise not to "commit any act intended to interfere with the Apple Software or related services," the company stated in a letter to the researcher.

"First they give researchers access to developer programs ... then they kick them out -- for doing research. Me angry," Miller posted on Twitter on Nov. 7. Miller, a principal consultant with security and compliance firm Accuvant, is no longer allowed to discuss the incident with press.

The debate about the best way to reveal software security flaws is more than two decades old. While the relationship between researchers and the software vendors whose product they investigate has always been uneasy, the tide appears to be taking a turn against researchers in 2011. Like Apple, companies once again are using tough tactics to take on researchers who point out vulnerabilities in their flaws.

"It seems the Grand Bargain is being breached," says Bruce Schneier, a noted security expert and chief security technology officer at British Telecom. "The retaliatory action by Apple is a good example."

The recent drama between Carrier IQ and security researcher Trevor Eckhart is another example. Eckhart's investigation spotlighted the fact that 141 million smartphones have quietly carried Carrier IQ's software to track phone performance as well as customer usage patterns. The software essentially represents a rootkit, allowing carriers -- and likely government agencies -- to access information about consumers' locations and use of phones.

Carrier IQ, unprepared for the intense media scrutiny following the revelations, took legal action against Eckhart, sending the researcher a cease-and-desist notice. After the Electronic Frontier Foundation agreed to represent Eckhart, however, the company backed off.

"As of today, we are withdrawing our cease and desist letter to Mr. Trevor Eckhart," the company stated. "We have reached out to Mr. Eckhart and the Electronic Frontier Foundation (EFF) to apologize."

Many of the companies affected by recent research are relatively new targets for researchers. The hardening of PC operating systems and applications has caused many researchers to focus on other platforms, such as medical devices, mobile phones, and even insulin pumps. The makers of those devices do not have the experience to deal with researchers as in the past.

"The full disclosure world takes a while to get use to," BT's Schneier says.

Such companies need to learn quickly that cultivating good relations with security researchers is the best way to weed out vulnerabilities from their systems. Microsoft took more than decade to develop good relations with researchers, but it's efforts have paid off. In 2011, the number of vulnerabilities publicly announced before Microsoft patched the underlying issue shrank for the third year in a row.

"Security researchers play an important role in helping Microsoft protect its customers and improve its products, as they offer unique expertise and insight," Jerry Bryant, group manager for Microsoft's Trustworthy Computing initiative, said in a statement.

Most recently, the company announced its BlueHat Prize for innovative defensive technologies in August and will award $200,000 to the best runtime mitigation technology.

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)