Its a Microsoft Virtual Machine security flaw. There is a patch for it, though I don't have the link to it off hand, but it isn't hard to find. Just go to the Microsoft Downloads page and type it in the "search" box.
It seems this comes along with the Java Runtime Environment. That's usually when I've encountered it anyways.
Hope this helps,
Cheers
Fnord, June 2005