# CVE-2013-6485: Memory corruption in n/a

> Remote attackers can crash Pidgin or potentially execute code via a buffer overflow in HTTP chunked transfer handling.

- **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:** 6 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-6485, GHSA-m3wf-vx8j-276c

## What is CVE-2013-6485?

CVE-2013-6485 is a medium-severity memory corruption vulnerability in Pidgin Pidgin, published on 6 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in util.c in libpurple in Pidgin before 2.10.8 allows remote HTTP servers to cause a denial of service (application crash) or possibly have unspecified other impact via an invalid chunk-size field in chunked transfer-coding data.

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

## Which versions are affected by CVE-2013-6485?

It affects 1 product.


Products: Pidgin Pidgin.

## How do I fix CVE-2013-6485?

Upgrade to a fixed version.

## Is CVE-2013-6485 being exploited?

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

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

## Sources

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

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