On Saturday 13 January 2007 16:39, Mike Miller wrote:
> On Fri, 12 Jan 2007, William Hooper wrote:
> >> What do we know about which VNC versions are vulnerable?
> >
> > Check it out using the CVE number:
> >
> > http://nvd.nist.gov/nvd.cfm?cvename=CVE-2006-2369
> >
> > This references the bug in ve
On Fri, 12 Jan 2007, William Hooper wrote:
What do we know about which VNC versions are vulnerable?
Check it out using the CVE number:
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2006-2369
This references the bug in version 4.1.1.
Thanks! That's what I thought. This note from Red Hat is fun
Mike Miller wrote:
> On Fri, 12 Jan 2007, Diana Hargus wrote:
>
>
>> Just had to clean up this new worm from an infected pc. Apparently the
>> vector was through an um-updated VNC on a friend's pc. Just another
>> reason to update and patch.
>>
>> http://www.us.sophos.com/security/analyses/w32rb
On Fri, 12 Jan 2007, Diana Hargus wrote:
Just had to clean up this new worm from an infected pc. Apparently the
vector was through an um-updated VNC on a friend's pc. Just another
reason to update and patch.
http://www.us.sophos.com/security/analyses/w32rbotgai.html
From the writeup on the
Hiyas,
Just had to clean up this new worm from an infected pc. Apparently the
vector was through an um-updated VNC on a friend's pc. Just another reason
to update and patch.
http://www.us.sophos.com/security/analyses/w32rbotgai.html
From the writeup on the worm at Sophos:
W32/Rbot-GAI s
