# CVE-2006-0635: Integer overflow in n/a

> A compiler bug in Tiny C Compiler causes incorrect evaluation of integer comparisons, potentially leading to integer overflow vulnerabilities in compiled applications.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0635, GHSA-vj7q-v8gv-98pv

## What is CVE-2006-0635?

CVE-2006-0635 is a medium-severity vulnerability in n/a, published on 10 Feb 2006. 

### Official description

Tiny C Compiler (TCC) 0.9.23 (aka TinyCC) evaluates the "i>sizeof(int)" expression to false when i equals -1, which might introduce integer overflow vulnerabilities into applications that could be exploited by context-dependent attackers.

## Which versions are affected by CVE-2006-0635?

It affects 1 product.


Products: Fabrice Bellard Tiny C Compiler.

## How do I fix CVE-2006-0635?

Upgrade to a fixed version.

## Is CVE-2006-0635 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0635 and fix it if it is affected.

What it is: CVE-2006-0635 is a medium-severity vulnerability in n/a, published on 10 Feb 2006. 
Exploitation: There is no known exploitation of CVE-2006-0635 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-2006-0635/ (Markdown: https://insights.sbomify.com/CVE-2006-0635/index.md)
```

## Sources

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

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