# CVE-2009-5029: Integer overflow in n/a

> An integer overflow in glibc's timezone file parser allows remote attackers to cause a crash or execute arbitrary code via a crafted TZ file.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 2 May 2013
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-5029, GHSA-m45f-chfc-x7hh

## What is CVE-2009-5029?

CVE-2009-5029 is a medium-severity vulnerability in Gnu Glibc, published on 2 May 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in the __tzfile_read function in glibc before 2.15 allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted timezone (TZ) file, as demonstrated using vsftpd.

Weakness: CWE-189

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

It affects 1 product.


Products: Gnu Glibc.

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

Upgrade to a fixed version.

## Is CVE-2009-5029 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5029 exists.

Public exploit code:

- GNU glibc - Timezone Parsing Remote Integer Overflow (exploitdb)

## 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-2009-5029 and fix it if it is affected.

What it is: CVE-2009-5029 is a medium-severity vulnerability in Gnu Glibc, published on 2 May 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5029 exists.

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-2009-5029/ (Markdown: https://insights.sbomify.com/CVE-2009-5029/index.md)
```

## Sources

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

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