Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Security IT

UK Mobile Operator O2 Leaks MMS Photos 154

Anonymous Hero writes "UK Mobile Operator O2 allows its customers to send Multimedia Messaging Service (MMS) photos to email recipients by way of a web interface. The URLs published by the MMS-to-email application are not authenticated, so a simple Google search reveals hundreds, if not thousands of private photos." Reader ttul points out similar coverage of this issue at InformationWeek.
This discussion has been archived. No new comments can be posted.

UK Mobile Operator O2 Leaks MMS Photos

Comments Filter:
  • by AHuxley ( 892839 ) on Saturday July 19, 2008 @02:27AM (#24251715) Journal
    I blame web 2.0 and young people.
    Back in the good old days you would have used safe ftp.
    ftp never hurt anyone.
    I do harbour dreams of being a Tor node operator.
  • by tecker ( 793737 ) on Saturday July 19, 2008 @02:37AM (#24251755) Homepage
    Cue lawsuit over this in

    3.....

    2.....

    1.....

    Ohhhh, settled out of court and everyone gets 1000 free picture and MMS messaging while we fix our system.



    (Im calling 3 weeks to the system being fixed)
  • Comment removed (Score:5, Insightful)

    by account_deleted ( 4530225 ) on Saturday July 19, 2008 @02:49AM (#24251799)
    Comment removed based on user account deletion
  • Re:Problem solved! (Score:4, Insightful)

    by duguk ( 589689 ) <dug@frag.co . u k> on Saturday July 19, 2008 @03:26AM (#24251915) Homepage Journal
    At least it might get O2's attention! All the action they've taken so far is deleting forum posts from their own forums and ignoring any email or telephone complaints.

    Are you really from the O2 Team? If so, I've got a few words for you...
  • by srjh ( 1316705 ) on Saturday July 19, 2008 @03:32AM (#24251943)
    Try searching for each of those 16-character IDs, and you'll see that each has already been posted publically, and most seem to be from just the one user. Which makes sense, if Google managed to index them in the first place.

    Sure, 02 should have taken steps to avoid being indexed, but they aren't responsible for leaking the photos.

    And It would be quite easy to write a script to try various combinations of 16 hex digits to try and randomly view a photo but depending on how many photos are being hosted the hit rate could be quite low.? Yeah, seeing as there are about 10^19 combinations, the hit rate would be fairly low. Did the author seriously consider this to be flaw?
  • by speedtux ( 1307149 ) on Saturday July 19, 2008 @03:32AM (#24251945)

    Worse still, the majority of the images taken on cameras turns out to be children. Ironically, O2 has a website dedicated to "Protect Our Children", well a good first step would be to avoid leaking customer photos.

    What bullshit idea is it that pictures of children need to be removed from the world? If you look at the history of photography, pictures of children have always been an important part of street photography, portraits, and artistic photography. In the US and many other places, it's legal to take pictures of children, even without permission of their parents. There are many pictures of children on Flickr and elsewhere.

    There is no evidence that pictures of children place them at risk. Can we please stop and reverse this meme that there is anything wrong with taking pictures of children?

    I don't really give a damn about pictures of children per se, but demonizing legitimate and legal content is a serious threat to free speech and democracy.

  • by Anonymous Coward on Saturday July 19, 2008 @03:33AM (#24251947)

    Since MMS can be sent to email directly from most handsets, does this actually affect anyone?

  • by duguk ( 589689 ) <dug@frag.co . u k> on Saturday July 19, 2008 @03:42AM (#24251983) Homepage Journal

    Sure, 02 should have taken steps to avoid being indexed, but they aren't responsible for leaking the photos.

    Their site is not suitabled secured, usually it would require a mobile number and pin code but this 16-digit code circumnavigates this requirement.

    From TFA, apparently these are also being picked up by Google's Toolbar.

    Surely if you'd MMS'd a friend a picture message, and they'd changed to a phone without MMS without you knowing - your picture will most likely be available on O2's website. Is this right? Should it be more secured? Or don't you care about who see's your 'private' conversations?

  • by LighterShadeOfBlack ( 1011407 ) on Saturday July 19, 2008 @05:02AM (#24252209) Homepage

    This is a SERIOUS breach of privacy. This will hit mainstream media. The fact that I can hit a google link and listen to people voice attachments, look at their photos - that's too public of a mistake. I look forward to watching this unfold.

    Umm... yesterday it hit the TV news that in the last 4 years the MoD has lost ~650 laptops - many containing classified information. It made the mainstream news, I'm sure people are moaning, and there'll probably be an "enquiry" which will take a few months and cost a few million eventually leading to nothing and, as always, nothing will change.

    By comparison a few photos and sound-bites is nothing. This will probably be a 1/8th page article on page 32 and that'll be the end of that.

    In the UK the prevalence of data collection is so great and the ineptitude of governments and companies is so absolute that this stuff is just commonplace now. Even if this story gets picked up anywhere it'll be overshadowed within days by a bigger data breach fuck-up somewhere else.

  • by Anonymous Coward on Saturday July 19, 2008 @05:39AM (#24252333)

    Aw, you gotta be kidding! You are not a sys admin, I suppose? ftp is a fucked up protocol (passive ftp? active ftp? gimme a break) that was a nightmare to manage, specially if you had firewalls.

  • by Cyberllama ( 113628 ) on Saturday July 19, 2008 @06:28AM (#24252471)

    You missed a key point in the TFA:

    I looked at the URL in the e-mail and found the only requirement was a 16 digit hex number. [Update: A few readers pointed out that a 64-bit key results in a HUGE number of possibilities to guess 10^19. However, as I can obtain the keys via another security hole no guessing is required - I'm not going to release that information yet as I'd like O2 to fix this]. As these web pages were wide open to the internet, not requiring any authentication a very small handful were indexed by Google. I was able to craft a Google search that results in some matches to show an example of how this is an insecure method of hosting:

    In other words, the stuff that's on google is merely the tip of the iceberg. He can start randomly plucking valid hex codes out of thin air and start viewing random people's random MMS's. The google search is just a "proof of concept" if you will, of the larger flaw.

    This could be, of course, untrue -- as we really only have his word to take for it that there is some "pattern" in picking valid hex codes.

  • by Anonymous Coward on Saturday July 19, 2008 @07:34AM (#24252657)

    Except for the extremely insecure daemon software that has allowed thousands, if not many more, servers to be rooted. And then there are the completely insane default security settings of many FTP servers (IIS anyone?) of yore.

    Also, FTP is difficult to firewall properly.

    There have even been exploitable bugs in Linux FTP conntrack module.

    Please, never ever associate FTP with good security. Use SFTP or HTTPS.

  • by Gandalf ( 787 ) on Saturday July 19, 2008 @09:04AM (#24252985) Homepage

    Their site is not suitabled secured, usually it would require a mobile number and pin code but this 16-digit code circumnavigates this requirement.

    I'd like to clarify this a bit to avoid that people think of the 16-digit code itself as insecure.

    Any site built with performance in mind has a similar setup: you authenticate yourself through the main site, but the content is on a delivery network. This network serves static files and by design doesn't handle the dynamics of authentication (cookies, HTTP auth).

    The idea is that using hard-to-guess ID tokens gives enough privacy: even if you were to guess or systematically scan them, you would get random content at best - you wouldn't have any information about the uploader or the context.

    Users with access to the content can of course republish it in ways that bypass the authentication, but that's true for all on-line content: once access has been granted to an authenticatied and authorised user, security becomes a matter of trust.

    The use of such IDs is not 100% secure but it's a good trade-off because ordinarily you have to be authenticated before you learn a specific ID.

    The real problem with the O2 site is the lack of authentication on the pages referencing the hard-to-guess IDs, not the use of IDs themselves.

    (The robots.txt omission isn't the real problem either, of course.)

"Look! There! Evil!.. pure and simple, total evil from the Eighth Dimension!" -- Buckaroo Banzai

Working...