Linked by Thom Holwerda on Wed 1st Jan 2014 19:11 UTC, submitted by jockm
Privacy, Security, Encryption

Remember when I wrote about how your mobile phone runs two operating systems, one of which is a black box we know and understand little about, ripe for vulnerabilities? As many rightfully pointed out in the comments - it's not just mobile phones that have tiny processors for specific tasks embedded in them. As it turns out, memory cards have microprocessors though - and yes, they can be cracked for remote code execution too.

Today at the Chaos Computer Congress (30C3), xobs and I disclosed a finding that some SD cards contain vulnerabilities that allow arbitrary code execution - on the memory card itself. On the dark side, code execution on the memory card enables a class of MITM (man-in-the-middle) attacks, where the card seems to be behaving one way, but in fact it does something else. On the light side, it also enables the possibility for hardware enthusiasts to gain access to a very cheap and ubiquitous source of microcontrollers.

There's so much computing power hidden in the dark.

Thread beginning with comment 579772
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Where's the story?
by DeepThought on Thu 2nd Jan 2014 11:36 UTC in reply to "Where's the story?"
DeepThought
Member since:
2010-07-17

So? What's the story here?

At first: It is a nice hack. Of course, I wonder how much time those guys did spend to do it.
And then: Every computer has an SD card reader, so with a "hacked" (but empty!) SD card I can get some troian horse into a computer: Plug it in, format it ("see, it is empty, no harm" :-). The next time some .exe is stored, it will be modified with the troian horse.

Reply Parent Score: 3

RE[2]: Where's the story?
by saso on Thu 2nd Jan 2014 13:29 in reply to "RE: Where's the story?"
saso Member since:
2007-04-18

This is nothing but a variation of the evil maid attack. Properly authenticating the data you read is always key, regardless if the corruption is intentional or accidental. Most checksummed filesystems will already defeat such an attempt, though it always helps to use some crypto-secure hash algorithm.

Reply Parent Score: 3

RE[3]: Where's the story?
by DeepThought on Fri 3rd Jan 2014 07:29 in reply to "RE[2]: Where's the story?"
DeepThought Member since:
2010-07-17

Most checksummed filesystems will already defeat such an attempt, though it always helps to use some crypto-secure hash algorithm.


Right, Didn't think of this. So the malware must know the filesystem.

Is NTFS checksummed?

Reply Parent Score: 1