# CVE-2010-4528: directconn.c in the MSN protocol plugin in libpurple 2.7.6 through 2.7.8 in Pidgin before 2.7.9 allows remote authenticated users to cause a


- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 7 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4528, GHSA-jmfm-mjhr-jhgw

## What is CVE-2010-4528?

CVE-2010-4528 is a medium-severity vulnerability in Pidgin Pidgin, published on 7 Jan 2011. 

### Official description

directconn.c in the MSN protocol plugin in libpurple 2.7.6 through 2.7.8 in Pidgin before 2.7.9 allows remote authenticated users to cause a denial of service (NULL pointer dereference and application crash) via a short p2pv2 packet in a DirectConnect (aka direct connection) session.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Pidgin Libpurple, Pidgin Pidgin.

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

Upgrade to a fixed version.

## Is CVE-2010-4528 being exploited?

There is no known exploitation of CVE-2010-4528 in the wild and no public exploit code.

## Other vulnerabilities in Pidgin Pidgin

- [CVE-2009-2703](https://insights.sbomify.com/CVE-2009-2703/): Null dereference in n/a (medium 5.0)
- [CVE-2009-3083](https://insights.sbomify.com/CVE-2009-3083/): Null dereference in n/a (medium 5.0)
- [CVE-2009-3084](https://insights.sbomify.com/CVE-2009-3084/): The msn_slp_process_msg function in libpurple/protocols/msn/slpcall.c in the MSN protocol plugin in libpurple 2.6.0 and 2.6.1, as used in Pi (medium 5.0)
- [CVE-2009-3085](https://insights.sbomify.com/CVE-2009-3085/): Denial of service in n/a (medium 5.0)
- [CVE-2011-3594](https://insights.sbomify.com/CVE-2011-3594/): Memory corruption in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4528 and fix it if it is affected.

What it is: CVE-2010-4528 is a medium-severity vulnerability in Pidgin Pidgin, published on 7 Jan 2011. 
Exploitation: There is no known exploitation of CVE-2010-4528 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-4528/ (Markdown: https://insights.sbomify.com/CVE-2010-4528/index.md)
```

## Sources

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

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