News for hackers. Stuff that matters.
Re:SMS Pumping Attack by jnwatson on Thursday August 03, 2023 @02:56AM (#36982296)
NIST recommended getting off SMS in 2016.

I’d say 7 years is plenty of time that folks really shouldn’t be using it.

https://www.schneier.com/blog/archives/2016/08/nist_is_no_lo...

Re:SMS Pumping Attack by ComodoHacker on Thursday August 03, 2023 @03:09AM (#36982386)
Meanwhile, there are countries whose entire banking, tax filing, CC processing and various public service systems rely on SMS as the only second factor.
Re:SMS Pumping Attack by vladvasiliu on Thursday August 03, 2023 @03:20AM (#36982465)
I don't know about those countries, but I know of one who says it's trying to compete with the US on tech, and one of their biggest banks moved away from hardware TOTP tokens to some kind of "secure app" and now to... SMS!

To name and shame: BNP in France. My personal account stayed on the app, but for my company account, it I only get SMS now.

Re:SMS Pumping Attack by KronisLV on Thursday August 03, 2023 @03:40AM (#36982579)
> To name and shame: BNP in France. My personal account stayed on the app, but for my company account, it I only get SMS now.

I remember a story about a university in Lithuania also opting for either SMS or a proprietary 2FA app, but not allowing TOTP either: https://fsfe.org/news/2023/news-20230418-01.html

What's worse, all they had to do was enable a checkbox in the settings somewhere but they went on an embarrassingly long e-mail thread back and forth, not even willing to help the users.

So I think that in cases like that, it's definitely a good idea to call attention to the issue and tell more people about open technologies like that! Unfortunately, most people just won't care.

That said, TOTP is actually decent and I'm surprised that it's not supported everywhere, especially given how much shouting about SMS not being secure enough goes around.

Re:SMS Pumping Attack by lxgr on Thursday August 03, 2023 @08:14AM (#36984759)
TOTP unfortunately does not satisfy the “transaction binding” requirement of PSD2, since the token does not tell you what you’re confirming at the time you share it with a (potentially MITMing) website.

SMS-OTP, despite its many other flaws, at least offers a trusted path to say “by sharing this code, you are paying x€ to y corp”.

Re:SMS Pumping Attack by vladvasiliu on Thursday August 03, 2023 @10:12AM (#36986230)
I think that since the issue at hand is that SMS can be intercepted, the protection afforded by this information is minimal.

Anecdotally, in the case of my bank, if I try to make a transfer, the SMS is something along the lines of "Are you trying to transfer 1234 €? If yes, enter the code 12345, or else call your representative asap".

One terrible point being that once you've entered the confirmation code, they consider the transaction as "strongly verified", so it's not that easy to roll it back. Fortunately, I've never had this happen to me so I don't know what that entails, but contesting a random unverified charge is as easy as clicking on the transaction list and then "dispute".

Re:SMS Pumping Attack by lxgr on Thursday August 03, 2023 @10:51AM (#36986761)
Yes, all in all I'm not happy with SMS-OTP still being considered just as secure as e.g. WebAuthN, and much more secure than Email-OTP (which is explicitly prohibited for PSD2/SCA purposes).

The problem isn't really interception in my view (even though SIM-jacking and porting attacks are scary enough!), but rather the high likelihood of phishing/UI confusion: With modern mobile OSes auto-filling transaction details, I'm not too sure if everybody is still reading the text accompanying the confirmation code.

It's quite possible for a fraud victim to be directed to amaz0n.com and tricked into entering an SMS-OTP confirmation code to confirm a purchase of €5.00, without noticing that the accompanying text actually says "only enter this code on BuyCryptoNoKycOrBacksies.com to confirm your purchase of €500".

Re:SMS Pumping Attack by Cthulhu_ on Thursday August 03, 2023 @03:42AM (#36982601)
That's also because these systems are large, complicated, and slow moving. Not only that, but the users are resistant to change; the older you get, the faster time moves, and a decade between one system (SMS) and the next (e.g. a two factor auth app) feels short and unnecessary.
Re:SMS Pumping Attack by ComodoHacker on Thursday August 03, 2023 @04:15AM (#36982844)
That's primarily because a significant portion of population there don't have smartphones.
Re:SMS Pumping Attack by lotsofpulp on Thursday August 03, 2023 @12:04PM (#36987723)
Last I checked, even the US federal government required SMS 2FA to get into your Social Security account.

But the problem is also only allowing SMS 2FA. Why not allow both and let people choose TOTP?

I have a feeling SMS 2FA is used as a cheap way to implement a rough social credit score. If you have a stable life and follow the rules, then you have continuous access to the same phone number. And only allowing SMS 2FA allows you to only deal with this population, and ignore populations that might have higher proportions of “costly” customers.

Re:SMS Pumping Attack by lxgr on Thursday August 03, 2023 @08:13AM (#36984739)
Very true, unfortunately.

My country’s administration lets people e-sign PDFs that are accepted throughout the EU as legally binding/equivalent to a paper signature using only a static password and SMS-OTP.

(The system used to be based on PCKS#11-compatible smart cards, but nobody managed to use the software, so they switched to SMS…)

Re:SMS Pumping Attack by ghusbands on Thursday August 03, 2023 @06:06AM (#36983709)
Sure, but it seems a bit short-sighted to assume that SMS brings no benefit. If a customer somehow loses access, SMS is far cheaper and more available for all involved than any other alternative. Most people don't want to carry any dongles (especially not institution-specific ones) and many don't really want to install apps or have phones that will wipe app data for infrequently-used apps.
Re:SMS Pumping Attack by bigDinosaur on Thursday August 03, 2023 @06:44AM (#36983954)
SMS as a backup is very different to SMS as your only option. For one it can be made much more inconvenient to use SMS so as to reduce the surface area for scams. Plenty of places still have it as the primary and only 2FA mechanism. Of course SMS itself is awful which is the key problem here. What you mean is that having your phone tied to an identity is useful (what if you lose your phone? SMS is no longer at all useful) and we could do much better than SMS for that.
Re:SMS Pumping Attack by berkes on Thursday August 03, 2023 @07:36AM (#36984349)
> SMS as a backup

Indeed. I once worked on a system where we had SMS as one of the "last resorts". When someone used SMS as recovery, we'd disable withdrawals and fundings (it was some sort of wallet) as well as severely limit their daily limits. Until the account was fully restored again using normal, secure methods (Mail, KYC, etc).

We were hit by a similar "attack" where our "let us call you to start recovery" was abused by putting a toll-number there, and our system would then call this toll-number and we'd get rediculous bills. But putting in limitations helped a lot, so we did this for SMS too.

Re:SMS Pumping Attack by ta1243 on Thursday August 03, 2023 @12:19PM (#36987921)
If I lose my phone I get a replacement simcard from my provider in a day or two, and SMS continues to work

If I lose my phone I've lost all my various OTP authenticator apps - I don't think they are backed up to icloud

Re:SMS Pumping Attack by bigDinosaur on Friday August 04, 2023 @07:53PM (#37007397)
You should be able to back up your OTP generator codes, I have mine in KeepassXC and on my phone.

Note as well that you really don't want to rely on SMS if travelling internationally, which is a use case I hit reasonably frequently.