# CVE-2009-1375: The PurpleCircBuffer implementation in Pidgin (formerly Gaim) before 2.5.6 does not properly maintain a certain buffer, which allows remote


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1375, GHSA-5p6v-j9j4-qvgx

## What is CVE-2009-1375?

CVE-2009-1375 is a medium-severity vulnerability in Pidgin Pidgin, published on 26 May 2009. 

### Official description

The PurpleCircBuffer implementation in Pidgin (formerly Gaim) before 2.5.6 does not properly maintain a certain buffer, which allows remote attackers to cause a denial of service (memory corruption and application crash) via vectors involving the (1) XMPP or (2) Sametime protocol.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2009-1375?

It affects 1 product.


Products: Pidgin Pidgin.

## How do I fix CVE-2009-1375?

Upgrade to a fixed version.

## Is CVE-2009-1375 being exploited?

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

## Other vulnerabilities in Pidgin Pidgin

- [CVE-2013-6490](https://insights.sbomify.com/CVE-2013-6490/): Memory corruption in n/a (critical 10.0)
- [CVE-2016-1000030](https://insights.sbomify.com/CVE-2016-1000030/): Code injection in n/a (critical 9.8)
- [CVE-2013-6486](https://insights.sbomify.com/CVE-2013-6486/): Command injection in n/a (critical 9.3)
- [CVE-2011-3185](https://insights.sbomify.com/CVE-2011-3185/): Command injection in n/a (critical 9.3)
- [CVE-2009-1376](https://insights.sbomify.com/CVE-2009-1376/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1375 and fix it if it is affected.

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

## Sources

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

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