[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PGP Desktop version 9.10.x-10.0.0 Insecure DLL Hijacking Vulnerability (tsp.dll, tvttsp.dll)
PGP Desktop version 9.10.x-10.0.0 Insecure DLL Hijacking
Vulnerability (tsp.dll, tvttsp.dll)
The PGP Desktop application is vulnerable to Insecure DLL Hijacking
Vulnerability. Similar terms that describe this vulnerability
have been come up with Remote Binary Planting, and Insecure DLL
2. PRODUCT DESCRIPTION
PGP Desktop Email provides enterprises with an automatic, transparent
encryption solution for securing internal and external confidential
email communications. With PGP Desktop Email, organizations can
minimize the risk of a data breach and comply with partner and
regulatory mandates for information security and privacy.
3. VULNERABILITY DESCRIPTION
The PGP Desktop application passes an insufficiently qualified path in
loading its external libraries - "tsp.dll, tvttsp.dll"
when a user opens its associated file with extensions - .p12, .pem,
.pgp, .prk, .prvkr, .pubkr, .rnd, .skr .
4. VERSIONS AFFECTED
Tested Platform: Windows XP Service Pack 3 (Fresh Windows)
Attackers can trigger a successful exploit against a victim user in a
number of ways such as placing a malicious external
library file made as hidden attribute and a seemingly interesting file
in network shares, usb drives, file sharing networks,
social networks, ..etc
Fixed version from the vendor has not been released yet.
However, it is suggested that the following workarounds be deployed by
users to protect increasing mass exploitation of this
- Disable loading of libraries from WebDAV and remote network shares
- Disable the WebClient service
Please see workaround solution links in References section.
This vulnerability was discovered by Aung Khant, http://yehg.net, YGN
Ethical Hacker Group, Myanmar.
10. DISCLOSURE TIME-LINE
09-09-2010: vulnerability discovered
09-09-2010: notified vendor
09-09-2010: vulnerability disclosed
Original Advisory URL:
Related: PGP 9.8 DLL Hijacking:
Workaround Solution: http://support.microsoft.com/kb/2264107
Testing for DLL Hijacking: