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

> Attackers can cause denial of service or execute arbitrary code in glibc via crafted internationalized domain names when libidn is enabled.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/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:** 26 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7424, GHSA-cf2r-3fcj-q45r, RHSA-2015:1627

## What is CVE-2013-7424?

CVE-2013-7424 is a medium-severity memory corruption vulnerability in Gnu Glibc, published on 26 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The getaddrinfo function in glibc before 2.15, when compiled with libidn and the AI_IDN flag is used, allows context-dependent attackers to cause a denial of service (invalid free) and possibly execute arbitrary code via unspecified vectors, as demonstrated by an internationalized domain name to ping6.

Weakness: CWE-17

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glibc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc-debuginfo-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc-headers` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc-utils` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `nscd` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-123.el5_11.3 |
| `glibc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `glibc-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `glibc-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `glibc-debuginfo-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `glibc-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `glibc-headers` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `glibc-utils` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |
| `nscd` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-123.el5_11.3 |

Products: Gnu Glibc.

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

Upgrade to a fixed version.

## Is CVE-2013-7424 being exploited?

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

## Other vulnerabilities in Gnu Glibc

- [CVE-2026-5450](https://insights.sbomify.com/CVE-2026-5450/): scanf %mc off-by-one heap buffer overflow (critical 9.8)
- [CVE-2023-25139](https://insights.sbomify.com/CVE-2023-25139/): Memory corruption in n/a (critical 9.8)
- [CVE-1999-0199](https://insights.sbomify.com/CVE-1999-0199/): Other in n/a (critical 9.8)
- [CVE-2019-1010022](https://insights.sbomify.com/CVE-2019-1010022/): Security feature bypass in glibc (critical 9.8)
- [CVE-2005-3590](https://insights.sbomify.com/CVE-2005-3590/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7424 is a medium-severity memory corruption vulnerability in Gnu Glibc, published on 26 Aug 2015. 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-7424 in the wild and no public exploit code.

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

## Sources

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

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