# CVE-2013-6483: Null dereference in n/a

> Remote attackers can crash Pidgin or spoof XMPP traffic via crafted IQ replies due to improper address validation in libpurple.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/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-6483, GHSA-7hf8-wq8c-mrxp

## What is CVE-2013-6483?

CVE-2013-6483 is a medium-severity 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

The XMPP protocol plugin in libpurple in Pidgin before 2.10.8 does not properly determine whether the from address in an iq reply is consistent with the to address in an iq request, which allows remote attackers to spoof iq traffic or cause a denial of service (NULL pointer dereference and application crash) via a crafted reply.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Pidgin Pidgin.

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

Upgrade to a fixed version.

## Is CVE-2013-6483 being exploited?

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

What it is: CVE-2013-6483 is a medium-severity 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-6483 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-6483/ (Markdown: https://insights.sbomify.com/CVE-2013-6483/index.md)
```

## Sources

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

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