First published: Fri Mar 18 2011(Updated: )
Open Ticket Request System (OTRS) before 2.4.10, and 3.x before 3.0.3, does not present warnings about incoming encrypted e-mail messages that were based on revoked PGP or GPG keys, which makes it easier for remote attackers to spoof e-mail communication by leveraging a key that has a revocation signature.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
OTRS | =3.0.0-beta1 | |
OTRS | =3.0.0-beta2 | |
OTRS | =3.0.0-beta3 | |
OTRS | =3.0.0-beta4 | |
OTRS | =3.0.0-beta5 | |
OTRS | =3.0.0-beta6 | |
OTRS | =3.0.0-beta7 | |
OTRS | =3.0.1 | |
OTRS | =3.0.2 | |
OTRS | <=2.4.9 | |
OTRS | =0.5-beta1 | |
OTRS | =0.5-beta2 | |
OTRS | =0.5-beta3 | |
OTRS | =0.5-beta4 | |
OTRS | =0.5-beta5 | |
OTRS | =0.5-beta6 | |
OTRS | =0.5-beta7 | |
OTRS | =0.5-beta8 | |
OTRS | =1.0-rc1 | |
OTRS | =1.0-rc2 | |
OTRS | =1.0-rc3 | |
OTRS | =1.0.0 | |
OTRS | =1.0.1 | |
OTRS | =1.0.2 | |
OTRS | =1.1-rc1 | |
OTRS | =1.1.0-rc1 | |
OTRS | =1.1.0-rc2 | |
OTRS | =1.1.1 | |
OTRS | =1.1.2 | |
OTRS | =1.1.3 | |
OTRS | =1.1.4 | |
OTRS | =1.2.0-beta1 | |
OTRS | =1.2.0-beta2 | |
OTRS | =1.2.0-beta3 | |
OTRS | =1.2.1 | |
OTRS | =1.2.2 | |
OTRS | =1.2.3 | |
OTRS | =1.2.4 | |
OTRS | =1.3.0-beta1 | |
OTRS | =1.3.0-beta2 | |
OTRS | =1.3.0-beta3 | |
OTRS | =1.3.0-beta4 | |
OTRS | =1.3.1 | |
OTRS | =1.3.2 | |
OTRS | =1.3.3 | |
OTRS | =2.0.0 | |
OTRS | =2.0.0-beta1 | |
OTRS | =2.0.0-beta2 | |
OTRS | =2.0.0-beta4 | |
OTRS | =2.0.0-beta5 | |
OTRS | =2.0.0-beta6 | |
OTRS | =2.0.1 | |
OTRS | =2.0.2 | |
OTRS | =2.0.3 | |
OTRS | =2.0.4 | |
OTRS | =2.0.5 | |
OTRS | =2.1.0-beta1 | |
OTRS | =2.1.0-beta2 | |
OTRS | =2.1.1 | |
OTRS | =2.1.2 | |
OTRS | =2.1.3 | |
OTRS | =2.1.4 | |
OTRS | =2.1.5 | |
OTRS | =2.1.6 | |
OTRS | =2.1.7 | |
OTRS | =2.1.8 | |
OTRS | =2.1.9 | |
OTRS | =2.2.0-beta1 | |
OTRS | =2.2.0-beta2 | |
OTRS | =2.2.0-beta3 | |
OTRS | =2.2.0-beta4 | |
OTRS | =2.2.0-rc1 | |
OTRS | =2.2.1 | |
OTRS | =2.2.2 | |
OTRS | =2.2.3 | |
OTRS | =2.2.4 | |
OTRS | =2.2.5 | |
OTRS | =2.2.6 | |
OTRS | =2.2.7 | |
OTRS | =2.2.8 | |
OTRS | =2.2.9 | |
OTRS | =2.3.0-beta1 | |
OTRS | =2.3.0-beta2 | |
OTRS | =2.3.0-beta3 | |
OTRS | =2.3.0-beta4 | |
OTRS | =2.3.0-rc1 | |
OTRS | =2.3.1 | |
OTRS | =2.3.2 | |
OTRS | =2.3.3 | |
OTRS | =2.3.4 | |
OTRS | =2.3.5 | |
OTRS | =2.3.6 | |
OTRS | =2.4.0-beta1 | |
OTRS | =2.4.0-beta2 | |
OTRS | =2.4.0-beta3 | |
OTRS | =2.4.0-beta4 | |
OTRS | =2.4.0-beta5 | |
OTRS | =2.4.0-beta6 | |
OTRS | =2.4.1 | |
OTRS | =2.4.2 | |
OTRS | =2.4.3 | |
OTRS | =2.4.4 | |
OTRS | =2.4.5 | |
OTRS | =2.4.6 | |
OTRS | =2.4.7 | |
OTRS | =2.4.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4764 has a medium severity rating as it allows attackers to spoof email communication due to the lack of warnings about revoked PGP or GPG keys.
To mitigate CVE-2010-4764, upgrade to OTRS version 2.4.10, 3.0.3, or later where the issue is addressed.
CVE-2010-4764 affects OTRS versions prior to 2.4.10 and any 3.x releases before 3.0.3.
The main issue with CVE-2010-4764 is the failure to alert users regarding incoming encrypted emails that are based on revoked keys, facilitating potential spoofing.
Users of OTRS systems that rely on PGP or GPG encryption for email communications are at risk from CVE-2010-4764.