# CVE-2009-3615: Denial of service in n/a > Remote attackers can crash Pidgin or Adium clients by sending crafted contact-list data via the OSCAR protocol. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Oct 2009 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2009-3615, DSA-1932-1, GHSA-vj8h-wj7f-5mcf, RHSA-2009:1536 ## What is CVE-2009-3615? CVE-2009-3615 is a medium-severity denial of service vulnerability in Pidgin Pidgin, published on 20 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The OSCAR protocol plugin in libpurple in Pidgin before 2.6.3 and Adium before 1.3.7 allows remote attackers to cause a denial of service (application crash) via crafted contact-list data for (1) ICQ and possibly (2) AIM, as demonstrated by the SIM IM client. Weakness: CWE-399 ## Which versions are affected by CVE-2009-3615? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `finch` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `libpurple` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `pidgin` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.6.3-2.el4 | | `finch` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `libpurple` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `pidgin` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.6.3-2.el4 | | `finch` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `libpurple` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `pidgin` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::es | All versions | 0:2.6.3-2.el4 | | `finch` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `finch-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `libpurple` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `libpurple-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `libpurple-perl` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `libpurple-tcl` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `pidgin` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `pidgin-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `pidgin-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | | `pidgin-perl` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.6.3-2.el4 | Products: Adium Adium, Pidgin Pidgin. ## How do I fix CVE-2009-3615? Upgrade to a fixed version. ## Is CVE-2009-3615 being exploited? There is no known exploitation of CVE-2009-3615 in the wild and no public exploit code. ## 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-2009-2694](https://insights.sbomify.com/CVE-2009-2694/): Memory corruption 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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2009-3615 and fix it if it is affected. What it is: CVE-2009-3615 is a medium-severity denial of service vulnerability in Pidgin Pidgin, published on 20 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2009-3615 in the wild and no public exploit code. 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-3615/ (Markdown: https://insights.sbomify.com/CVE-2009-3615/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-3615 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-3615 - OSV: https://osv.dev/vulnerability/CVE-2009-3615 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-3615/ Summaries are generated and may contain mistakes; the official description above is the record.