Risk
9/4/2010
01:38 PM
George V. Hulme
George V. Hulme
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Apple's Ping Stumble Highlights Systemic Security Problem

Within 48 hours of Ping's launch, Apple's foray into music social networks, more than one million users joined. Too bad, like so many other applications and services on the Internet, security was an afterthought, and those users were plagued with spam comments.

Within 48 hours of Ping's launch, Apple's foray into music social networks, more than one million users joined. Too bad, like so many other applications and services on the Internet, security was an afterthought, and those users were plagued with spam comments.Chester Wisniewski's blog post (anti-virus vendor Sophos), shows users getting inundated with "Get a free iPhone from . . . " spam because Apple failed to adequately authenticate users,or filter bogus URLs, in the new service:

Strangely, Apple seems to have anticipated a certain degree of malfeasance, as profile pictures that you upload will not appear until approved by Apple. They are likely filtering for other offensive content as well, so they probably have means in place they could use to stop the spam. Another problem that is likely to contribute to spam is that it is quite easy to create bogus accounts for the Ping service because no credit card or other positive identification is required to participate.

Coincidentally, the most common spam on Ping at the moment targets Apple itself. The attacks are nearly identical to survey spams we have blogged about on Facebook, Google and Twitter.

If half as many free iPads, iPhones and iPods were being given away as Ping comments might lead you to believe, there would be no reason to bother with going to an Apple store. But if you actually want an Apple device, my advice is to go out and buy one, as filling out surveys will likely only end in tears.

Our Thomas Claburn covered the Apple spam slip-up in some depth in his story Apple iTunes Ping Draws Spam, Complaints.

To its credit, Apple does appear to now be cleaning spam from its systems. However, Apple loses points for not seeing this coming. Spam that hawks gadgets and other wares is a big problem on Twitter, while in the early days of the now defunct Google Wave complaints of spam slowing the system surfaced, and we all know that comment spam is a big scourge on blogging sites.

Which brings us to a broader, much more important question: why is security, when it comes to just about any application or service deployed on the Internet, treated as the red-headed stepchild that is ignored until something bad happens?

Security was ignored when industry moved all of its back-end applications to the Web in the late 1990s and early 2000s - and Web application security is still abysmal, if not worse, today. Same is true with online credit card acceptance. It didn't take a genius of a futurist to predict that credit card thievery and fraud would follow commerce to the Internet in the late 1990s - and yet merchants and the credit card industry didn't do much to secure e-Commerce systems. It wasn't until 2005 when the Payment Card Industry Data Security Standard came into being - about a decade after online commerce started its growth.

It's because designing secure systems is a difficult (much harder than breaking them by comparison) additional step. It requires engineers step back and consider how the system they're building can possibly be infiltrated, abused and misused. And then design must be changed to mitigate those risks. And it also requires incremental layers of quality control - scanning for defects in design and code during development and as the application lives and changes in production.

That's, apparently, still too much to expect. Speaking of design defects, if you haven't yet, you should consider updating to iTunes 10 - the upgrade comes with a fix for a baker's dozen of separate software vulnerabilities.

One of the most recent, similar examples, of such security design fail and social networking site Twitter, which I covered earlier this summer in the post FTC Security Smackdown And Twitter's Hollow Excuses.

Despite its early security lapses, you can find me on Twitter, and follow my security and business observations throughout the day.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2009-5142
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in timthumb.php in TimThumb 1.09 and earlier, as used in Mimbo Pro 2.3.1 and other products, allows remote attackers to inject arbitrary web script or HTML via the src parameter.

CVE-2010-5302
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in timthumb.php in TimThumb before 1.15 as of 20100908 (r88), as used in multiple products, allows remote attackers to inject arbitrary web script or HTML via the QUERY_STRING.

CVE-2010-5303
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in the displayError function in timthumb.php in TimThumb before 1.15 (r85), as used in multiple products, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to $errorString.

CVE-2014-3562
Published: 2014-08-21
Red Hat Directory Server 8 and 389 Directory Server, when debugging is enabled, allows remote attackers to obtain sensitive replicated metadata by searching the directory.

CVE-2014-3577
Published: 2014-08-21
org.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.