# CVE-2009-2694: Memory corruption in n/a > Remote attackers can execute arbitrary code or cause denial of service in Pidgin and Adium via crafted MSNSLP messages due to memory corruption. - **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Aug 2009 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2009-2694, DSA-1870-1, GHSA-gg6v-c4q4-582f, RHSA-2009:1218 ## What is CVE-2009-2694? CVE-2009-2694 is a critical memory corruption vulnerability in Pidgin Pidgin, published on 20 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The msn_slplink_process_msg function in libpurple/protocols/msn/slplink.c in libpurple, as used in Pidgin (formerly Gaim) before 2.5.9 and Adium 1.3.5 and earlier, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) by sending multiple crafted SLP (aka MSNSLP) messages to trigger an overwrite of an arbitrary memory location. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2009-1376. Weakness: CWE-399 ## Which versions are affected by CVE-2009-2694? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pidgin` | Red Hat:enterprise_linux:3::as | All versions | 0:1.5.1-4.el3 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.5.1-4.el3 | | `pidgin` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.5.1-4.el3 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.5.1-4.el3 | | `pidgin` | Red Hat:enterprise_linux:3::es | All versions | 0:1.5.1-4.el3 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.5.1-4.el3 | | `pidgin` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.5.1-4.el3 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.5.1-4.el3 | | `finch` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `libpurple` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `pidgin` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.5.9-1.el4 | | `finch` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `libpurple` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `pidgin` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.5.9-1.el4 | | `finch` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `libpurple` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `pidgin` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::es | All versions | 0:2.5.9-1.el4 | | `finch` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.5.9-1.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.5.9-1.el4 | Products: Adium Adium, Pidgin Pidgin. ## How do I fix CVE-2009-2694? Upgrade to a fixed version. ## Is CVE-2009-2694 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2694 exists. Public exploit code: - Pidgin MSN 2.5.8 - Remote Code Execution (exploitdb) ## Other vulnerabilities in Pidgin Pidgin - [CVE-2008-7190](https://insights.sbomify.com/CVE-2008-7190/): Cross-site scripting in n/a (critical 10.0) - [CVE-2010-0013](https://insights.sbomify.com/CVE-2010-0013/): Path traversal in n/a (high 7.5) - [CVE-2008-2927](https://insights.sbomify.com/CVE-2008-2927/): Integer overflow in n/a (medium 6.8) - [CVE-2010-0277](https://insights.sbomify.com/CVE-2010-0277/): Memory corruption in n/a (medium 5.0) - [CVE-2009-3615](https://insights.sbomify.com/CVE-2009-3615/): Denial of service in n/a (medium 5.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2009-2694 and fix it if it is affected. What it is: CVE-2009-2694 is a critical memory corruption vulnerability in Pidgin Pidgin, published on 20 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2694 exists. Affected product: Pidgin Pidgin. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2009-2694/ (Markdown: https://insights.sbomify.com/CVE-2009-2694/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-2694 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-2694 - OSV: https://osv.dev/vulnerability/CVE-2009-2694 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-2694/ Summaries are generated and may contain mistakes; the official description above is the record.