First published: Tue Sep 04 2001(Updated: )
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 has already been signed by the third party, aka the "PGPsdk Key Validity Vulnerability."
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
PGP (Pretty Good Privacy) | =7.0.3 | |
PGP E-Business Server | =6.5.8 | |
PGP Corporate Desktop | =7.1 | |
PGP (Pretty Good Privacy) | =6.0.2 | |
PGP (Pretty Good Privacy) | =5.0 | |
PGP (Pretty Good Privacy) | =7.0.3 | |
PGP E-Business Server | =7.1 | |
PGP E-Business Server | =7.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2001-1016 has been classified as a medium severity vulnerability due to the risk of misleading users regarding document authenticity.
To mitigate CVE-2001-1016, upgrade to PGP Corporate Desktop version 7.1 or higher, Personal Security version 7.0.3 or higher, or Freeware version 7.0.3 or higher.
CVE-2001-1016 affects PGP Corporate Desktop versions prior to 7.1, Personal Security prior to 7.0.3, Freeware prior to 7.0.3, and E-Business Server prior to 7.1.
CVE-2001-1016 can be exploited by attackers who create documents with invalid userIDs, potentially misleading users into believing they are signed by a trusted source.
Yes, CVE-2001-1016 is related to user authentication issues, as it involves the improper validation of userIDs when signing messages.