# CVE-2013-6413: Use after free in n/a

> Remote attackers can crash the UnrealIRCd server via a use-after-free vulnerability, causing a denial of service.

- **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:** No
- **Published:** 19 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q59v-wxhw-jhqw

## What is CVE-2013-6413?

CVE-2013-6413 is a medium-severity use after free vulnerability in n/a, published on 19 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free vulnerability in UnrealIRCd 3.2.10 before 3.2.10.2 allows remote attackers to cause a denial of service (crash) via unspecified vectors.  NOTE: this identifier was SPLIT per ADT2 due to different vulnerability types. CVE-2013-7384 was assigned for the NULL pointer dereference.

Weakness: CWE-399

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

It affects 1 product.


Products: Unrealircd Unrealircd.

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

No fix has been published for CVE-2013-6413 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-6413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-7144](https://insights.sbomify.com/CVE-2016-7144/): Auth bypass in n/a (high 8.1)
- [CVE-2023-50784](https://insights.sbomify.com/CVE-2023-50784/): Memory corruption in n/a (high 7.5)
- [CVE-2010-2075](https://insights.sbomify.com/CVE-2010-2075/): Supply chain in n/a (high 7.5)
- [CVE-2009-4893](https://insights.sbomify.com/CVE-2009-4893/): Memory corruption in n/a (medium 6.8)
- [CVE-2017-13649](https://insights.sbomify.com/CVE-2017-13649/): Privilege escalation in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6413 and fix it if it is affected.

What it is: CVE-2013-6413 is a medium-severity use after free vulnerability in n/a, published on 19 May 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-6413 in the wild and no public exploit code.

Affected product: n/a. 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-6413/ (Markdown: https://insights.sbomify.com/CVE-2013-6413/index.md)
```

## Sources

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

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