Live data from Hacker News

Hacking Transcend WiFi SD Cards

haxit.blogspot.com

11–20 of 58 posts

Re: Hacking Transcend WiFi SD Cards

#11
post #2

My experience with embedded systems allows me to be fairly certain that this bugfest is due to an electronics engineer writing the software for the card. Way too often small R&D teams, especially working on new products, have EE people being assigned to part-time-embedded-programmer roles. This is especially scary as some of these teams work on internet-facing pieces of hardware - home routers/gateways, etc. One cool…

[deleted]

Re: Hacking Transcend WiFi SD Cards

#13
post #6
post #2

My experience with embedded systems allows me to be fairly certain that this bugfest is due to an electronics engineer writing the software for the card. Way too often small R&D teams, especially working on new products, have EE people being assigned to part-time-embedded-programmer roles. This is especially scary as some of these teams work on internet-facing pieces of hardware - home routers/gateways, etc. One cool…

As someone who's written software for all his life, I'll posit that most "software engineers" write code like this. People don't test corner cases; they just shit out code, check that it works in the browser, and ship it. That's why the regexes like /.PNG/ are in there: they work, but they don't prevent the security problems they intend to prevent. If the engineer writing the code had written unit tests that checked…

Ultimately, I'm not complaining, because buggy software is great in the context of devices that try to prevent you from doing something with your own property. I especially encourage people to write their system-level software in C and use lots of strcpy calls. It ensures that I can root my phone even though the carrier doesn't want me to.

Reminds me of claims of deliberate backdoors. Of course, these can often be used for bad things too.

Re: Hacking Transcend WiFi SD Cards

#14
post #2

My experience with embedded systems allows me to be fairly certain that this bugfest is due to an electronics engineer writing the software for the card. Way too often small R&D teams, especially working on new products, have EE people being assigned to part-time-embedded-programmer roles. This is especially scary as some of these teams work on internet-facing pieces of hardware - home routers/gateways, etc. One cool…

There's an old saying I don't hear much these days: never give a software engineer a soldering iron and never give a hardware engineer a compiler.

Re: Hacking Transcend WiFi SD Cards

#15
Contrived, sure, but you could use these exploits to upload all files added to the card somewhere, assuming it can find a wireless network to connect to. Maybe even just keep a hidden copy on the part of the FS invisible to the host system if there is enough free space.

"Oh sure I've got an SD card you can borrow..."

Re: Hacking Transcend WiFi SD Cards

#18
post #6
post #2

My experience with embedded systems allows me to be fairly certain that this bugfest is due to an electronics engineer writing the software for the card. Way too often small R&D teams, especially working on new products, have EE people being assigned to part-time-embedded-programmer roles. This is especially scary as some of these teams work on internet-facing pieces of hardware - home routers/gateways, etc. One cool…

As someone who's written software for all his life, I'll posit that most "software engineers" write code like this. People don't test corner cases; they just shit out code, check that it works in the browser, and ship it. That's why the regexes like /.PNG/ are in there: they work, but they don't prevent the security problems they intend to prevent. If the engineer writing the code had written unit tests that checked…

Another explanation is that there is no benefit to the manufacturer in writing tighter code. Tighter code means more time spent on testing and review, but probably wouldn't increase sales. From a bottom line point of view, the mantra is get it working and ship it.

Re: Hacking Transcend WiFi SD Cards

#20
"Perl has a nice feature when opening a file with the open() library call, because it not only opens files, but runs programs if the file path is not a path, but a shell command ending in a pipe."

I thought only PHP did things like that :)

I hope this is disabled in mod_perl? Because if not I need to let someone know they need to audit their code.

PS. I get how useful this is, and it's well documented, but this functionality should be in the ancillary function (i.e. used when needed), not in the default one.

Post reply on HN