First published: Wed Aug 08 2012(Updated: )
cipher.c in the Cipher API in libpurple in Pidgin before 2.7.10 retains encryption-key data in process memory, which might allow local users to obtain sensitive information by reading a core file or other representation of memory contents.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pidgin | =2.5.9 | |
Pidgin | =2.5.8 | |
Pidgin | =2.7.5 | |
Pidgin | =2.7.0 | |
Pidgin | =2.10.1 | |
Pidgin | =2.1.0 | |
Pidgin | =2.7.4 | |
Pidgin | =2.6.0 | |
Pidgin | =2.5.2 | |
Pidgin | =2.5.1 | |
Pidgin | =2.7.6 | |
Pidgin | =2.5.6 | |
Pidgin | =2.5.7 | |
Pidgin | =2.0.1 | |
Pidgin | =2.4.2 | |
Pidgin | <=2.7.9 | |
Pidgin | =2.7.3 | |
Pidgin | =2.5.4 | |
Pidgin | =2.10.2 | |
Pidgin | =2.5.5 | |
Pidgin | =2.6.5 | |
Pidgin | =2.2.2 | |
Pidgin | =2.1.1 | |
Pidgin | =2.3.1 | |
Pidgin | =2.4.3 | |
Pidgin | =2.6.6 | |
Pidgin | =2.0.0 | |
Pidgin | =2.0.2 | |
Pidgin | =2.3.0 | |
Pidgin | =2.4.1 | |
Pidgin | =2.4.0 | |
Pidgin | =2.6.2 | |
Pidgin | =2.5.0 | |
Pidgin | =2.10.4 | |
Pidgin | =2.2.0 | |
Pidgin | =2.2.1 | |
Pidgin | =2.7.8 | |
Pidgin | =2.10.0 | |
Pidgin | =2.7.7 | |
Pidgin | =2.5.3 | |
Pidgin | =2.6.1 | |
Pidgin | =2.6.4 | |
Pidgin | =2.7.2 | |
Pidgin | =2.10.3 | |
Pidgin | =2.7.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2011-4922 is categorized as medium due to the potential exposure of sensitive encryption key data.
To fix CVE-2011-4922, upgrade Pidgin to version 2.7.10 or later where the vulnerability has been addressed.
CVE-2011-4922 affects Pidgin versions prior to 2.7.10, including versions such as 2.5.0 to 2.7.9.
CVE-2011-4922 is a local information disclosure vulnerability that allows unauthorized access to sensitive encryption keys from memory.
No, CVE-2011-4922 requires local access to the system to exploit the vulnerability.