# CVE-2010-0277: Memory corruption in n/a

> Remote attackers can cause denial of service or potential code execution in Pidgin and Adium via malformed MSN protocol messages.

- **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:** 9 Jan 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0277, GHSA-rj5f-77wg-8qgv

## What is CVE-2010-0277?

CVE-2010-0277 is a medium-severity memory corruption vulnerability in Pidgin Pidgin, published on 9 Jan 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

slp.c in the MSN protocol plugin in libpurple in Pidgin before 2.6.6, including 2.6.4, and Adium 1.3.8 allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly have unspecified other impact via a malformed MSNSLP INVITE request in an SLP message, a different issue than CVE-2010-0013.

Weakness: CWE-399

## Which versions are affected by CVE-2010-0277?

It affects 2 products.


Products: Adium Adium, Pidgin Pidgin.

## How do I fix CVE-2010-0277?

Upgrade to a fixed version.

## Is CVE-2010-0277 being exploited?

There is no known exploitation of CVE-2010-0277 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-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-2010-0277 and fix it if it is affected.

What it is: CVE-2010-0277 is a medium-severity memory corruption vulnerability in Pidgin Pidgin, published on 9 Jan 2010. 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-2010-0277 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-2010-0277/ (Markdown: https://insights.sbomify.com/CVE-2010-0277/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0277
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0277
- OSV: https://osv.dev/vulnerability/CVE-2010-0277

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0277/
Summaries are generated and may contain mistakes; the official description above is the record.