CVE-2001-1016: High severity PGP Corporate Desktop vulnerability

Published Sep 4, 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."

Affected Software

8 affected components
PGP Corporate Desktop=7.1
PGP E-Business Server=6.5.8
PGP E-Business Server=7.0.4
PGP E-Business Server=7.1
PGP Freeware=7.0.3
PGP Personal Security=7.0.3
PGP PGP=5.0
PGP PGP=6.0.2

Event History

Sep 4, 2001
CVE Published
04:00 AM
Mar 9, 2002
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2001-1016?

CVE-2001-1016 has been classified as a medium severity vulnerability due to the risk of misleading users regarding document authenticity.

2

How do I fix CVE-2001-1016?

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.

3

What software is affected by CVE-2001-1016?

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.

4

What type of attack can exploit CVE-2001-1016?

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.

5

Is CVE-2001-1016 related to user authentication?

Yes, CVE-2001-1016 is related to user authentication issues, as it involves the improper validation of userIDs when signing messages.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203