CVE-2012-3374
pidgin: Stack-based buffer overwrite in MXit protocol libPurple plug-in
Overview
Description
Buffer overflow in markup.c in the MXit protocol plugin in libpurple in Pidgin before 2.10.5 allows remote attackers to execute arbitrary code via a crafted inline image in a message.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Weakness: CWE-119
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 6 fixes
debian 4 releases · 1 package
fixed 4
pidgin
| Release | Package | Fixed in |
|---|---|---|
| 11 | pidgin | 2.10.6-1 |
| 12 | pidgin | 2.10.6-1 |
| 13 | pidgin | 2.10.6-1 |
| 14 | pidgin | 2.10.6-1 |
echo 1 release · 1 package
fixed 1
pidgin
| Release | Package | Fixed in |
|---|---|---|
| pidgin | 2.10.6-1 |
openSUSE 1 release · 1 package
fixed 1
finch
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | finch +9 | 2.11.0-4.1 | openSUSE-SU-2024:10432-1 |
References
- hg.pidgin.im http://hg.pidgin.im/pidgin/main/rev/ded93865ef42
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2012-07/msg00009.html
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2012-1102.html
- secunia.com http://secunia.com/advisories/50005
- www.mandriva.com http://www.mandriva.com/security/advisories?name=MDVSA-2012:105
- www.pidgin.im http://www.pidgin.im/news/security/?id=64
- www.pidgin.im http://www.pidgin.im/news/security/index.php?id=64
- access.redhat.com https://access.redhat.com/security/cve/CVE-2012-3374
- linux.oracle.com https://linux.oracle.com/cve/CVE-2012-3374.html
- linux.oracle.com https://linux.oracle.com/errata/ELSA-2012-1102.html
Show all 14 references
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.