Skip to content
Noroxi
CVE-2007-0640· NVD / CVE Program· CNA mitre

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

CriticalCVSS 10.0 · v2.0—No exploit Fix available
Published
Jan 31, 2007
Updated
Jun 16, 2026
EPSS
2.0% · 80th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

41

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.0%

Affected systems

VendorProduct
zabbixzabbix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • zabbix zabbixup to 1.1.4 inclusive
  • zabbix zabbix1.1.2
  • zabbix zabbix1.1.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12zabbixbefore 1:1.1.4-81:1.1.4-8

Same product

zabbix: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-23131Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAMLKEV
    98Now
  • CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV
    80Now
  • CVE-2016-10134SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the t
    64This week
  • CVE-2024-42327SQL injection in user.get API
    63This week
  • CVE-2013-5743Multiple SQL injection vulnerabilities in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7.
    63This week
  • CVE-2024-22120Time Based SQL Injection in Zabbix Server Audit Log
    58Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:zabbix1:1.1.4-8 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
C · data can be read
Integrity
C · data or configuration can be modified
Availability
C · the service can be disrupted
Attack complexity
Low
Confidentiality impact
C
Integrity impact
C
Availability impact
C

Weakness class (CWE)

—

CVSS vector

AV:N/AC:L/Au:N/C:C/I:C/A:C

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records