Title: PGP Invalid Key Display Vulnerability
Severity: HIGH
Description:
PGP Security provides privacy and data confidentiality software.
There is a vulnerability in some of PGP's display of key validity which could allow a user to be tricked into accepting a signature created by an invalid user ID.
When there are two user ID's on the same key, PGP's display heuristically communicates key validity to the user. The first strategy is to base the validity display on the first user ID in the key. The second is to base the validity display on the most valid key.
The key verification window's name field uses the first strategy, while the validity light on this display uses the second strategy. Thus, when a key having an invalid user ID as the primary name and a valid user ID as the secondary name is displayed, it shows the primary user's name, but the validity of the secondary name.
If such a key is sent to a user who relies on the affected validity displays, the key may appear to be valid. If the key is imported into the target user's keyring, attackers can forge signatures on documents sent to the target user as the invalid user-id.
Affected Products:
- Network Associates PGP 5.0.0
- Network Associates PGP 6.0.2
- Network Associates PGP Corporate Desktop 7.1.0
- Network Associates PGP E-Business Server 6.5.8
- Network Associates PGP E-Business Server 7.0.4
- Network Associates PGP E-Business Server 7.1.0
- Network Associates PGP Freeware 7.0.3
- Network Associates PGP Personal Security 7.0.3
References:
- Blue Ring Software: A security Analysis of PGP
- PGP Security: PGPsdk Key Validity Vulnerability
Juniper Networks provides this content via a wide variety of sources and production methods. If notified of errors or omissions in the content of this page, Juniper Networks, at its discretion, will modify or remove the page or leave the content as is, depending on various factors including but not limited to the reputation and authority of the party providing the notification. Please use the contact information displayed elsewhere on this page to report any errors or omissions regarding the content on this page.
