O2 binds Bluebook SMS security bug
Yet more URL manipulation mischief
O2 has plugged a security hole that allowed customers to view text messages sent by other UK subscribers online.
The issue involves O2's Bluebook application, which allows subscribers to save any text messages they send or receive for viewing online. Coding errors in Bluebook created a means for registered users to view other user's messages (and phone numbers) simply by changing the message ID number in URLs used to access messages on the site. In a statement, the mobile phone giant said that it has fixed the problem.
"We have identified and closed a loophole in Bluebook which allowed O2 Bluebook customers logged into their own account to view the message of another Bluebook customer by changing the URL in the browser window. This allowed them – in one particular window only - to view a random text message of another Bluebook user and in some cases the phone number of the sender," an O2 spokeswoman explained.
O2 said the security slip-up emerged as the "result of an internal review" on Friday 8 February. It said the loophole was closed on Monday 11 February. The issue was reported to us by Reg reader Tom, who claimed that the issue was actually reported to O2 on 4 February.
The mobile phone operator apologised for the slip-up, adding that it had implemented unspecified security measures to guard against similar coding problems in future.
"We apologise to our Bluebook customers for this lapse. We have conducted a thorough review to make sure it cannot happen again and that their details are secure," the spokewoman added.
Flaws that leave customer data viewable by simple URL manipulation are a common coding mistake, and one that 02 itself has fallen victim to in the past. The mobile phone giant was obliged to disable logins to its Bill Manager website in August 2006 when it emerged that registered users could see other customers' call records. The service, which allows small businesses to manage their spending on mobile calls, was subject to much the same URL manipulation coding snafu as the Bluebook site. The slip-up exposed sensitive call records, though more sensitive billing records were not accessible through the application and therefore not exposed.
URL manipulation also opened the way for the curious to view the details of applicants applying for jobs at oil giant Shell in Jan 2003. More seriously, the same class of vulnerability exposed credit card details of customers of utility Powergen back in July 2000. ®
Disgraceful, O2 should be ashamed?
Why should O2 be ashamed? They didn't write the bluebook application. I have it on strong authority that they are using a third party piece of software from a company called newbay called lifecache to host bluebook, so it is not their coding error, it is the fault of a third party and all blame should lie with them.
I'll confirm I reported this on the 4th
I reported this, but I didn't post it to the media as I thought it was somewhat irresponsible to do so and once fixed it is kind of a moot point really.
It was fixed by the end of Monday 11th and my initial phone call was.... 5pm-ish Monday 4th February. I asked to speak to a manager, they rang me back at 7pm. Midday Tuesday another manager rang for permission to give my details to someone else. Someone else rang me on Wednesday, I emailed them screenshots and a description around 4.20pm Wednesday. Tuesday 12th had a voicemail from the same someone else to check the problem was solved.
Without doubt the hardest part was explaining that this wasn't just a case of someone else using my computer and me needing to clear my cache.
I know! and as for basic English mistakes such as 'athe information via a form post instead '! Heads should roll!