[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.21.0610250424510.20582-100000@linuxbox.org>
Date: Wed, 25 Oct 2006 04:30:18 -0500 (CDT)
From: Gadi Evron <ge@...uxbox.org>
To: bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk
Subject: Re: Yahoo! Messenger Service 18 Remote Buffer Overflow Vulnerability
>
> Does anyone have more information on this issue?
>
Yes. SecuriTeam is currently assisting a researcher with reporting this
issue to Yahoo! security.
Yahoo! security responded in record time, as they often do, and are
working to resolve this potential security vulnerability.
An official report with full credit to the researcher who discovered it
will be released when the incident has been resolved.
A similar vulnerability was reported on the mailing lists a few months
ago, which has not been fixed. SecuriTeam assisted the researcher and
Yahoo! responded and fixed the issue in a matter of a day. Yahoo! are very
capable with security vulnerabilities in their software.
Thanks,
Gadi.
> ----snip----
> http://www.securityfocus.com/bid/20625/discuss
> Yahoo! Messenger is prone to a remote buffer-overflow vulnerability
> because it fails to properly bounds-check user-supplied data before
> copying it to an insufficiently sized memory buffer.
>
> This vulnerability allows remote attackers to execute arbitrary machine
> code in the context of the affected application. Failed exploit attempts
> will likely crash the server, denying further service to legitimate
> users.
>
> Yahoo! Messenger 8 with Voice is vulnerable.
> ----snip----
>
>
> I could not find this vulnerability reported on any other place than
> bugtraq (say Secunia, iDefense, ISC).
>
>
> Thanks,
>
> - Siddhartha
>
Powered by blists - more mailing lists