![]() ![]() ![]() |
|
dclegg:
And we're all OK with this?
Seems like a pretty serious breach of personal data. Email is far from a secure medium. At the very least, it should require an authenticated session before allowing it to be viewed.
Follow up: Is there a way to opt out of these electronic bills? I can't seem to find any option to do so via MySpark.
I guess if someone is making lots of dodgy 0900 for sex calls, then it looks a bit off if someone gets your invoice. But, in the days of internet do those even exist any longer?
How do I get the bill of someone considerably more famous than myself? It is an issue for them perhaps.
The issue I have is that there is enough info on a bill to be able to initiate a number port, and that is apparently an acceptable source of 2FA for banks and stuff, so while you are on hold with spark about why your phone isnt working, someone could be cleaning out your accounts, logging into the google etc with a SMS 2 factor etc.
surfisup1000:
I guess if someone is making lots of dodgy 0900 for sex calls, then it looks a bit off if someone gets your invoice. But, in the days of internet do those even exist any longer?
How do I get the bill of someone considerably more famous than myself? It is an issue for them perhaps.
Privacy issues aside, what if someone gets hold of your bill and leverages the information to gain access to your Spark account? They then use this information to gain access to other services you own. This is how identity theft starts.
We obviously need it to become a more common occurrence here in New Zealand before people start to be more proactive or concerned about it. But it is a big deal overseas.
Good news. Hopefully someone opens my bill and pays it for me
mendit:
Good news. Hopefully someone opens my bill and pays it for me
Or uses it to get more information about you from Spark through social engineering, then uses that information to call your bank and drain your bank account.
Loose lips may sink ships - Be smart - Don't post internal/commercially sensitive or confidential information!
@dclegg:
Privacy issues aside, what if someone gets hold of your bill and leverages the information to gain access to your Spark account? They then use this information to gain access to other services you own. This is how identity theft starts.
How do you go about doing this?
Other than in the movie, it requires a bit more than pressing a few button on the keyboards.
nakedmolerat:
How do you go about doing this?
Other than in the movie, it requires a bit more than pressing a few button on the keyboards.
Going about getting the bill? Or leveraging the information once done?
For the former, it'd be trivial to write an app to perform a HTTP GET using the base URL, incrementing the UUID for each request. For any responses that return a PDF, you have a hit. Save that to file, and use the information later. If the URLs really do take 18 months to expire, it may be feasible to be able to crack a few of these with enough hardware thrown at the problem (disclaimer: I've not done the math on this, but it would be interesting to do so).
And nefarious cracking attempts aside, what about accidental sharing of the URL? E.g. sending it to your partner via email or TXT, but sending to the wrong recipient.
For the latter, there is enough information on there to use social engineering to gain access to the users Spark account. And considering the amount of users out there that use an ISP email (we still do), that will unlock access to even more of the users information and accounts.
I'll say it again, I'm quite surprised that more people aren't concerned about this. I'd expect it from the general public, but not from the more technically minded folks here. The same that do acknowledge that companies storing passwords in plain text in their databases are a security risk.
richms:
I would assume that there are brute force prevention measures on the bills as you have on a password etc. It is a huge string too.
I would've also assumed that clicking on my bill URL would throw up an authentication challenge, but this assumption was incorrect (and what motivated me to investigate further). So I wouldn't necessarily assume this is true.
One such brute force prevention measure would be to have expiring URLs. But if these do really last 18 months, it's almost as bad as having no expiry.
I concede it is a huge string. So as I said, it would be interesting to crunch the numbers to see how long it would take to generate a successful hit.
dclegg:
richms:
I would assume that there are brute force prevention measures on the bills as you have on a password etc. It is a huge string too.
I would've also assumed that clicking on my bill URL would throw up an authentication challenge, but this assumption was incorrect (and what motivated me to investigate further). So I wouldn't necessarily assume this is true.
One such brute force prevention measure would be to have expiring URLs. But if these do really last 18 months, it's almost as bad as having no expiry.
I concede it is a huge string. So as I said, it would be interesting to crunch the numbers to see how long it would take to generate a successful hit.
it depends on how they're generating it (how much entropy there is) and how long it is.
If it is a 128 bit GUID and it's securely generated, then the answer is "a very long time" and certainly it would be noticed
@dclegg:
Going about getting the bill? Or leveraging the information once done?
For the former, it'd be trivial to write an app to perform a HTTP GET using the base URL, incrementing the UUID for each request. For any responses that return a PDF, you have a hit. Save that to file, and use the information later. If the URLs really do take 18 months to expire, it may be feasible to be able to crack a few of these with enough hardware thrown at the problem (disclaimer: I've not done the math on this, but it would be interesting to do so).
As noted above - the link only lasts for 1 month. It may be feasible still - but the effort is worth it? Really?
And nefarious cracking attempts aside, what about accidental sharing of the URL? E.g. sending it to your partner via email or TXT, but sending to the wrong recipient.
You can make the same error with PDF attachment.
For the latter, there is enough information on there to use social engineering to gain access to the users Spark account. And considering the amount of users out there that use an ISP email (we still do), that will unlock access to even more of the users information and accounts.
Sure - this however depends on the information that they need. It is probably easier to get that from somewhere else than cracking those URL just to get your phone bills.
I'll say it again, I'm quite surprised that more people aren't concerned about this. I'd expect it from the general public, but not from the more technically minded folks here. The same that do acknowledge that companies storing passwords in plain text in their databases are a security risk.
As mentioned many times in this thread - the risk is no worse than resetting your password using email address etc.
I think the 18 month thing could do with looking at however. That seems absurdly long. Accessing past bills is an ideal way to make people log in etc when you can then present them with offers etc so I would expect a link to become invalid as soon as the next bill is issued.
|
![]() ![]() ![]() |