It's not an "NFC" hack. It's a terminal hack over NFC. The first time I saw this article I thought there was something wrong in the NFC protocol or one of the NFC applications.
Really? Here stolen cards are used everyday by people either wearing a helmet, masks, or nothing at all.
They even bomb the ATMs, and never get caught. Don't trust that the police catches these guys most of the time. And don't trust banks who say they only got away with a few hundred bucks.
Re:ATM NFC Hack
by aliasEli on Friday June 25, 2021 @04:40AM
(#27628420)
Yet another buffer overflow. Probably the software is written by some C/C++ developers who swear that those never occur in their code. Given the large number of security problems that have been caused by buffer overflows and similar problems, I find it very sad that any programs that need security are still written in C/C++.
While you're technically correct, your ignoring the pragmatic truth: most developers are terrible and should never write code. Because of this reality, C/C++ and all its footguns are something to be avoided unless there is no other alternative (usually this happens when integrating with legacy software or in industries like gaming where the switching costs are extreme).
Re:ATM NFC Hack
by junon on Sunday June 27, 2021 @06:02AM
(#27650159)
So you're saying that since we're encouraging people to flood the market with little to no skill, we should instead accommodate them with Baby's First Programming Language and then force all of the other developers to follow the same methodology?
Re:ATM NFC Hack
by agumonkey on Sunday June 27, 2021 @07:55AM
(#27650847)
terrible programmers ain't nothing new though and large corp in critical fields are aware of that and have (or had) structural mitigations (slow and heavy processes, regulations etc)
Re:ATM NFC Hack
by IshKebab on Sunday June 27, 2021 @05:47AM
(#27650084)
This is sort of true, but show me a (non-trivial) C++ program that doesn't resort to naked pointers or references at some point.
In the real world, smart pointers help a lot and are a great idea but they don't fully solve the problem in the same way that Rust or memory safe languages do.
If you can’t be trusted to handle basic, simple non-creative tasks like managing memory and buffers you are not actually a professional programmer, though you might have convinced an employer otherwise.
Re:ATM NFC Hack
by paavohtl on Sunday June 27, 2021 @04:49AM
(#27649799)
By this logic no C or C++ developer in history is a professional programmer. Approximately zero non-trivial programs have been written in C or C++ without memory management problems and/or vulnerabilities.
But given all the cameras on and around an ATM this would be a quick way to living your life looking over your shoulder.
This makes no sense. It just sounds like Go.
In the real world, smart pointers help a lot and are a great idea but they don't fully solve the problem in the same way that Rust or memory safe languages do.
Look up software verification. There are verifiers for C.
It's the "fault" of the programmer, but the language makes it very easy to make these faults, so I'd say it's the fault of the language.