Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security FullDisclosure
[Top] [All Lists]

Re: [Full-disclosure] Google Talk cleartext credentials in process memor

Subject: Re: [Full-disclosure] Google Talk cleartext credentials in process memory
Date: Tue, 29 Nov 2005 10:22:00 +0000
Personally I only tested the "patched" version by searching for the
ASCII (decimal) representation of my own password.

In other words, I searched for "mypassword" with a hex editor, rather
than its hexadecimal representation "6d7970617373776f7264"

If what you're saying is that all Google did is change the
cleartext password to its hexadecimal representation then you might be
completely right as I haven't tested this myself.

Anyways, if that's the case, then shame on Google for such a poor
attempt of obfuscation.

On 11/29/05, 6ackpace <6ackpace@gmail.com> wrote:

Hi,

If i am right Google Talk Beta Messenger cleartext credentials in process
memory still exist on the current version.
googles answer for this issue:
plain char -> hex char



6ackpace
On 11/29/05, Jaroslaw Sajko <sloik@parareal.net> wrote:

pagvac wrote:
Title: Google Talk Beta Messenger cleartext credentials in process
memory


Description

Google Talk stores all user credentials (username and password) in
clear-text in the process memory. Such vulnerability was found on
August 25, 2005 (two days after the release of Google Talk) and has
already been patched by Google.

This issue would occur regardless of whether the "Save Password"
feature was enabled or not.

The same issue concerns many applications, ie. Gadu-Gadu - another
instant messenger. In my opinion such "vulnerabilities" are not worthy
publishing (for Gadu-Gadu we have not published this kind of software
behaviour) because if you can dump other user process or trick him to
execute any code then reading the password from the process memory is
only one of many things which you can do.

regards,
js
_______________________________________________
Full-Disclosure - We believe in it.
Charter:
http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/





--
pagvac (Adrian Pastor)
www.ikwt.com - In Knowledge We Trust


--
pagvac (Adrian Pastor)
www.ikwt.com - In Knowledge We Trust
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

<Prev in Thread] Current Thread [Next in Thread>