# CVE-2007-3508: Integer overflow in n/a

> Local attackers might execute arbitrary code via integer overflow in glibc's environment variable processing, though exploitability is disputed.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-3508, GHSA-r68c-v3gr-w2rh

## What is CVE-2007-3508?

CVE-2007-3508 is a high-severity vulnerability in n/a, published on 3 Jul 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in the process_envvars function in elf/rtld.c in glibc before 2.5-rc4 might allow local users to execute arbitrary code via a large LD_HWCAP_MASK environment variable value.  NOTE: the glibc maintainers state that they do not believe that this issue is exploitable for code execution

Weakness: CWE-189

## Which versions are affected by CVE-2007-3508?

It affects 1 product.


Products: Gentoo Glibc.

## How do I fix CVE-2007-3508?

Upgrade to a fixed version.

## Is CVE-2007-3508 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3508 and fix it if it is affected.

What it is: CVE-2007-3508 is a high-severity vulnerability in n/a, published on 3 Jul 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3508 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-2007-3508/ (Markdown: https://insights.sbomify.com/CVE-2007-3508/index.md)
```

## Sources

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

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