what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

googleTalk.txt

googleTalk.txt
Posted Dec 1, 2005
Authored by pagvac aka Adrian Pastor | Site ikwt.com

Google Talk Beta Messenger stores all credentials in clear text in the process memory.

tags | advisory
SHA-256 | 77351e323ebc2b62b46a2bc7cd97d4de54156ea418e6b6aeaadbc17bf1698b51

googleTalk.txt

Change Mirror Download
Title: Google Talk Beta Messenger cleartext credentials in process memory

Affected versions: 1.0.0.64 (this version is believed to be the first one released to the public)

Vendor contacted: 25/08/05

Patched version released: 29/08/05

Advisory released: 28/11/05

Author: pagvac (Adrian Pastor)

Homepage: www.ikwt.com - In Knowledge We Trust

Advisory URL: www.adrianpv.com/projects/google-talk-cleartext-credentials-in-process-memory.txt



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.

It was noticed that the Google Talk client was loading all the credentials unencrypted in the memory of the process "googletalk.exe". It was possible to recover the password by dumping the process memory to a file with PMDump and which could then examined with a hex editor.

The vulnerability would allow anyone with access to the client system to obtain the username and password of the current user. This vulnerability could also be exploited by fooling the user to execute malicious code which would dump the memory of the process "googletalk.exe" and then parse the credentials and finally send them to the attacker.

It is also worth mentioning that sometimes, no direct user interaction is required for the execution of malicious code. Crackers often exploit vulnerabilities in web browsers and email clients that allow them to execute malicious code on the victim's machine without requiring the victim to manually execute the trojaned executable. This means that given the right scenario, this vulnerability could have been exploited in such a way.



References

PMDump - https://ntsecurity.nu/toolbox/pmdump/
Free Hex Editor - https://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
Google Talk - https://www.google.com/talk/
Login or Register to add favorites

File Archive:

September 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Sep 1st
    261 Files
  • 2
    Sep 2nd
    17 Files
  • 3
    Sep 3rd
    38 Files
  • 4
    Sep 4th
    52 Files
  • 5
    Sep 5th
    23 Files
  • 6
    Sep 6th
    27 Files
  • 7
    Sep 7th
    0 Files
  • 8
    Sep 8th
    1 Files
  • 9
    Sep 9th
    16 Files
  • 10
    Sep 10th
    38 Files
  • 11
    Sep 11th
    21 Files
  • 12
    Sep 12th
    40 Files
  • 13
    Sep 13th
    18 Files
  • 14
    Sep 14th
    0 Files
  • 15
    Sep 15th
    0 Files
  • 16
    Sep 16th
    21 Files
  • 17
    Sep 17th
    51 Files
  • 18
    Sep 18th
    23 Files
  • 19
    Sep 19th
    48 Files
  • 20
    Sep 20th
    36 Files
  • 21
    Sep 21st
    0 Files
  • 22
    Sep 22nd
    0 Files
  • 23
    Sep 23rd
    0 Files
  • 24
    Sep 24th
    0 Files
  • 25
    Sep 25th
    0 Files
  • 26
    Sep 26th
    0 Files
  • 27
    Sep 27th
    0 Files
  • 28
    Sep 28th
    0 Files
  • 29
    Sep 29th
    0 Files
  • 30
    Sep 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2024 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close