Pgp Corporate Desktop vulnerabilities

4 known vulnerabilities affecting pgp/corporate_desktop.

Total CVEs
4
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH3MEDIUM1

Vulnerabilities

Page 1 of 1
CVE-2007-0603HIGHCVSS 7.1v9.52007-01-30
CVE-2007-0603 [HIGH] CVE-2007-0603: PGP Desktop before 9.5.1 does not validate data objects received over the (1) \pipe\pgpserv named pi PGP Desktop before 9.5.1 does not validate data objects received over the (1) \pipe\pgpserv named pipe for PGPServ.exe or the (2) \pipe\pgpsdkserv named pipe for PGPsdkServ.exe, which allows remote authenticated users to gain privileges by sending a data object representing an absolute pointer, which causes code execution at the corresponding address.
nvd
CVE-2002-0850HIGHCVSS 7.5v7.1.12002-10-04
CVE-2002-0850 [HIGH] CVE-2002-0850: Buffer overflow in PGP Corporate Desktop 7.1.1 allows remote attackers to execute arbitrary code via Buffer overflow in PGP Corporate Desktop 7.1.1 allows remote attackers to execute arbitrary code via an encrypted document that has a long filename when it is decrypted.
nvd
CVE-2002-0788MEDIUMCVSS 5.5v7.12002-08-12
CVE-2002-0788 [MEDIUM] CWE-459 CVE-2002-0788: An interaction between PGP 7.0.3 with the "wipe deleted files" option, when used on Windows Encrypte An interaction between PGP 7.0.3 with the "wipe deleted files" option, when used on Windows Encrypted File System (EFS), creates a cleartext temporary files that cannot be wiped or deleted due to strong permissions, which could allow certain local users or attackers with physical access to obtain cleartext information.
nvd
CVE-2001-1016HIGHCVSS 7.5v7.12001-09-04
CVE-2001-1016 [HIGH] CVE-2001-1016: PGP Corporate Desktop before 7.1, Personal Security before 7.0.3, Freeware before 7.0.3, and E-Busin PGP Corporate Desktop before 7.1, Personal Security before 7.0.3, Freeware before 7.0.3, and E-Business Server before 7.1 does not properly display when invalid userID's are used to sign a message, which could allow an attacker to make the user believe that the document has been signed by a trusted third party by adding a second, invalid user ID to a key which
nvd