# CVE-2007-0640: Memory corruption in n/a

> A buffer overflow in Zabbix allows attackers to potentially execute arbitrary code or cause denial of service via SNMP IP addresses.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 31 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-0640, GHSA-c3fc-hggh-m873

## What is CVE-2007-0640?

CVE-2007-0640 is a critical memory corruption vulnerability in Zabbix Zabbix, published on 31 Jan 2007. It can be exploited over the network.

### Official description

Buffer overflow in ZABBIX before 1.1.5 has unknown impact and attack vectors related to "SNMP IP addresses."

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

It affects 1 product.


Products: Zabbix Zabbix.

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

Upgrade to a fixed version.

## Is CVE-2007-0640 being exploited?

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

## Other vulnerabilities in Zabbix Zabbix

- [CVE-2022-23131](https://insights.sbomify.com/CVE-2022-23131/): Zabbix Frontend Authentication Bypass (critical 9.1, exploited in the wild)
- [CVE-2024-42327](https://insights.sbomify.com/CVE-2024-42327/): SQL injection in user.get API (critical 9.9)
- [CVE-2024-22116](https://insights.sbomify.com/CVE-2024-22116/): Remote code execution within ping script (critical 9.9)
- [CVE-2013-3738](https://insights.sbomify.com/CVE-2013-3738/): Code injection in n/a (critical 9.8)
- [CVE-2013-5743](https://insights.sbomify.com/CVE-2013-5743/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0640 is a critical memory corruption vulnerability in Zabbix Zabbix, published on 31 Jan 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-0640 in the wild and no public exploit code.

Affected product: Zabbix Zabbix. 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-0640/ (Markdown: https://insights.sbomify.com/CVE-2007-0640/index.md)
```

## Sources

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

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