CVE-2024-42332 | New line injection in Zabbix SNMP traps

The researcher is showing that due to the way the SNMP trap log is parsed, an attacker can craft an SNMP trap with additional lines of information and have forged data show in the Zabbix UI. This attack requires SNMP auth to be off and/or the attacker to know the community/auth details. The attack requires an SNMP item to be configured as text on the target host.

Published: 2024-11-27 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-42332 is rated Low Risk (30.1/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.62%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-42332

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.91% 0.62% -0.29%
2 2026-06-06 0.84% 0.91% +0.06%
3 2026-05-30 — 0.84% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-42332

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.7 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 1.4 [email protected]

Weakness enumeration for CVE-2024-42332

OS Trackers for CVE-2024-42332

vendor priority summary link
alpine — CVE-2024-42332: 1 source package rows (zabbix); 3 state rows across 3 repos (3.20-community, 3.22-community, edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2024-42332
debian not yet assigned CVE-2024-42332 not yet assigned priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-42332
suse medium CVE-2024-42332 severity moderate: SUSE including 2 source package names (zabbix, zabbix-agent), 7 product×package rows across 5 product lines (SUSE Linux Enterprise Server 12 SP4-LTSS, SUSE Linux Enterprise Server 12 SP5-LTSS, … (5 product lines)): Known Not Affected 7. https://www.suse.com/security/cve/CVE-2024-42332/
ubuntu medium CVE-2024-42332 medium priority: Ubuntu including 1 source packages (zabbix), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 5, not-affected 2, DNE 1, ignored 1, released 1. https://ubuntu.com/security/CVE-2024-42332

Affected software / configurations for CVE-2024-42332

Vendor Product Version Raw CPE
zabbix zabbix >= 6.0.0, < 6.0.35 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 6.4.0, < 6.4.20 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 7.0.0, < 7.0.3 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*

References for CVE-2024-42332

cvelogic Threat Intelligence