Server Help :: View topic - Headlines (including JPEG vulnerability)

Server Help

Trash Talk - Headlines (including JPEG vulnerability)

CypherJF - Wed Sep 15, 2004 10:14 am
Post subject: Headlines (including JPEG vulnerability)

Quote:

KDan writes "As reported by numerous sources, a new vulnerability has been disclosed (and patched) by Microsoft. This one concerns the parsing of JPEGs in XP Microsoft applications. A buffer overflow can be used to execute arbitrary code. So all those times you told your parents/friends that looking at images was safe - well, not anymore."

http://www.vnunet.com/news/1158095

Lexar JumpDrive, "Secure". Not anymore.

Quote:

Saint Aardvark writes "Lexar describes the JumpDrive Secure as "loaded with software that lets you password-protect your data. If lost or stolen, you can rest assured that what you've saved there remains there with 256-bit AES encryption." @stake has a different take: The password can be observed in memory or read directly from the device, without evidence of tampering." And best of all, the punch line: "[The password] is stored in an XOR encrypted form and can be read directly from the device without any authentication." That's why I use ROT-13 for my encryption needs."

http://www.atstake.com/research/advisories/2004/a091304-1.txt

new's retreived from slashdot.org

Cyan~Fire - Wed Sep 15, 2004 4:21 pm
Post subject:

Secure, a Qndre product.

Dr Brain - Wed Sep 15, 2004 5:08 pm
Post subject:

C'mon now, Cyan, be nice.

At least they shipped a product.

Solo Ace - Wed Sep 15, 2004 5:13 pm
Post subject:

What's wrong with Qndre products?

We all know everything Qndre *ahem* "created" *ahem* was great.

CypherJF - Wed Sep 15, 2004 6:17 pm
Post subject:

Btw, Dr Brain: I like your avatar

Cyan~Fire - Wed Sep 15, 2004 7:01 pm
Post subject:

Actually, I am going to be a bit nicer.

@stake wrote:

The Safe Guard
software takes care of the decryption and the password can be seen in plain text within memory when the software does a compare between the stored password and the supplied password.

Well the password does have to be plain-text in memory at some point. The measure of security is how long it stays there, and it doesn't state that in this report.

Bak - Wed Sep 15, 2004 9:06 pm
Post subject:

it doesn't have to compare it in plain text though... like comparing hashes would be better

Cyan~Fire - Thu Sep 16, 2004 12:44 am
Post subject:

That is true, but then you can always generate a matching hash.

Mine GO BOOM - Thu Sep 16, 2004 1:49 am
Post subject:

Cyan~Fire wrote:

That is true, but then you can always generate a matching hash. :-)

In the case of reversing SS passwords if they are even, or reversing just a word in which will hash the same, reversing to plaintext is always worse. Lost of people use the same password for everything, so getting one of their passwords in plain text is very bad. Just finding a possible word in which will hash to the same for just that one application isn't bad, as you won't be able to guess their bank/ebay passwords with that. Of course, if they are securing their USB stick, their passwords are probably already on that thing encrypted, which you'll now be able to decrypt.

Bak - Thu Sep 16, 2004 1:49 am
Post subject:

Quote:

That is true, but then you can always generate a matching hash.

not for any good hashing function. That's the whole big deal when they found a way to find collisions in MD5's hash a few weeks ago in less than an hour on a regular machine.

If you're writing software that's primary purpose is security and you're hashing stuff a strong hash function is a must.

SuSE - Thu Sep 16, 2004 2:42 am
Post subject:

jpeg, not jpg

CypherJF - Thu Sep 16, 2004 9:53 am
Post subject:

Sorry - edited.

SuSE - Thu Sep 16, 2004 10:00 am
Post subject:

YOU'RE DAMN RIGHT EDITED

CypherJF - Thu Sep 16, 2004 10:01 am
Post subject:

rotfl

Smong - Sat Sep 18, 2004 1:43 pm
Post subject:

Scaremongers.