- Apr 4, 2001
- 2,776
- 0
- 0
Originally posted by: So
yes, due to yet another bug found in windows. Any other OS is safe
Originally posted by: Shagga
Originally posted by: So
yes, due to yet another bug found in windows. Any other OS is safe
Is that right? I didn't think you could...
Originally posted by: n0cmonkey
Originally posted by: Shagga
Originally posted by: So
yes, due to yet another bug found in windows. Any other OS is safe
Is that right? I didn't think you could...
You don't pay much attention do you?
Originally posted by: Shagga
Originally posted by: n0cmonkey
Originally posted by: Shagga
Originally posted by: So
yes, due to yet another bug found in windows. Any other OS is safe
Is that right? I didn't think you could...
You don't pay much attention do you?
Obviously not. So yet another MS problem. The point being of course that in theory you cannot get a virus within a jpg file normally. It's just that MS enables you to do so!!
Originally posted by: The Boss
Nobody is putting a gun on your head. If you dont like MS Windows, don't use it.
Originally posted by: The Boss
Nobody is putting a gun on your head. If you dont like MS Windows, don't use it.
Originally posted by: hans007
i had heard this was a flaw with the way jpegs are decoded, and affects pretty much all systems that decode jpegs. its a buffer over flow problem.
the buffer over flows, with the right instructions placed to replace the return instruction pointer. theres been some talk of it at my work, some guys analyzing this stuff. pretty interesting. the code is out, for how to make your own jpeg that exploits this or something like that.
another day another bug.
Originally posted by: Fritzo
An example of a virus in a jpg (don't worry, it's safe)
Originally posted by: sandorski
Originally posted by: hans007
i had heard this was a flaw with the way jpegs are decoded, and affects pretty much all systems that decode jpegs. its a buffer over flow problem.
the buffer over flows, with the right instructions placed to replace the return instruction pointer. theres been some talk of it at my work, some guys analyzing this stuff. pretty interesting. the code is out, for how to make your own jpeg that exploits this or something like that.
another day another bug.
Yes, it's another IE vulnerabilty, non MS browsers don't have this issue.
Dump IE all, it's a frickin seive.
