• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Keylogger in a .avi file?

Recently, I saw a post over on DAoC Catacombs where an individual claimed that he had his DAoC account names and passwords were stolen with a keylogger embedded in an avi file. Here is his exact claim:

I am paying the price for not having my windows XP updated - my accounts were stolened and then deleted after I hit an RvR video with a nice keylogger embedded in the .avi file - an executable that had I been more thourough on my updates I would have never gotten.

My question is, how is this possible? I was under the assumption that an .avi video cannot make calls to the system or any .exe... It just played.

If this is possible; how can it be prevented from happening?

Thanks for any insight.
 
Well, I don't know anything about this, but certainnly AVI files aren't SUPPOSED to allow you to do such things, but it is always possible that windows had a flaw where you could trick it into letting you execute code.
 
Originally posted by: BrownTown
Well, I don't know anything about this, but certainnly AVI files aren't SUPPOSED to allow you to do such things, but it is always possible that windows had a flaw where you could trick it into letting you execute code.

It was a very well known security issue with windows media player.

Let's put it this way - if you accept any data, of any kind, in any way, wheter with or without your permission...code that you don't authorize can be run. Especially if you don't patch rigorously as soon as they are released.

scooby - look up "buffer overflow" or "remote code executiion".

To prevent look at the consolidated security thread in the Software forum.

-edit-
this is high tech forum so I'll try my best even though I'm not a programmer...

1) you receive data that you requested (or in a WORM, you never requested it) as a user.
2) this stream contains information in it to take advantage of a process that doesn't know what to do with the overflow of information that it has stored in a memory buffer. An unchecked buffer overflow.
3) processor's "what do I execute next" points to this code in memory. Remember a processor just says "what do I do next, where do I go, where did I come from, what is my next instruction" (stack)
4) this "bad" code is now in memory and the processor goes ahead and executes it

That's my best non-high tech explation. I'm sure lots of really smart people can put it better. But in the end, binary code, regardless of user privelages is executed because the "bad thing" occurs below the operating system by taking advantage of a bug in the operating system or application.
 
Yeah, that's about right...

We actually had a lab for a senior level microcontroller apps class where we had to create a buffer overrun and generate code to execute and get around a password (in a set-up program, of course). That was kinda fun.

Basically it works if your buffer for user input is placed in the wrong location in memory so that when it is overfilled code can be run to do... whatever.
 
OH yes brown, exactly right. The took a program that has hundreds of thousands of lines of code and didn't debug it at all. Because after all, every security issue and buffer flow vulnerability would be found if they'd just take a minute to do it......

Or not.
 
Originally posted by: LsDPulsar
OH yes brown, exactly right. The took a program that has hundreds of thousands of lines of code and didn't debug it at all. Because after all, every security issue and buffer flow vulnerability would be found if they'd just take a minute to do it......

Or not.

woah, no need to get all up in arms about it. But this is a VERY popular piece of software that is on millions of computers. Now we all know that bugs can happen and stuff, but you would still hope that on something so basic they could manage to avoid such issues.
 
Originally posted by: phisrow
I don't think that this applies to .avi files; but .wmv files are disconcertingly vulnerable in an unusual way. If their DRM flag is set, they'll automatically attempt to acquire a license. This means that opening a .wmv can do a surprising amount of other things, by design no less.

Example: http://www.securityfocus.com/archive/1/386829/2005-01-10/2005-01-16/0
You can embed links into a WMV and do redirection (tool is free in the Windows Media Encoder suite). I would more suspect a WMV than an AVI too. But, it may take other vulnerabilities to get that code to infect a machine. Chances are that that guy is not up to date on MS patches.

 
Back
Top