dbcve.org
ZabbixApplication

CVE-2024-22122

CRITICAL · 9.1 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to after 6.4.15 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Zabbix allows to configure SMS notifications. AT command injection occurs on "Zabbix Server" because there is no validation of "Number" field on Web nor on Zabbix server side. Attacker can run test of SMS providing specially crafted phone number and execute additional AT commands on modem.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Zabbix Server contains an AT command injection vulnerability in its SMS notification feature. Due to missing input validation on the 'Number' field (both on the web interface and server-side), an attacker with access to the SMS test functionality can inject arbitrary AT commands into the modem by providing a specially crafted phone number.

MitigationImplement strict input validation and sanitization for the phone number field, using an allowlist of permitted characters (digits, plus sign, dashes) and rejecting any characters that could be interpreted as AT command separators.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZabbixApplication
Affected:>= 5.0.0, <= 5.0.42>= 6.0.0, <= 6.0.30>= 6.4.0, <= 6.4.15= 7.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Zabbix version
    Access Zabbix web interface: go to Administration > Reports > Audit log, or check via API: apiinfo.version. Alternatively, check the Zabbix server or frontend package version using system commands like 'zabbix_server --version' or review the frontend footer in the login page.
    Affected if The installed version falls within 5.0.0-5.0.42, 6.0.0-6.0.30, 6.4.0-6.4.15, or 7.0.0 exactly.
  2. Verify SMS media type exists
    In Zabbix web interface, navigate to Alerts > Media types. Look for media types with type 'SMS' (GSM modems). Check if any SMS media type is defined and enabled.
    Affected if An SMS media type is configured and enabled in the Zabbix installation.
  3. Confirm SMS testing functionality is accessible
    In Zabbix web interface, go to Alerts > Media types > SMS row, and click 'Test' button. Alternatively, check user permissions under Administration > Users > User or Role settings for permissions to 'execute scripts' or 'test media' operations.
    Affected if The logged-in user has permissions to test SMS notifications or execute media type tests.
  4. Inspect SMS gateway configuration
    Check the Zabbix server configuration file (zabbix_server.conf) for SMS-related parameters: DB, DBHost, SNMPTrapperFile, and external script paths. Also review /usr/lib/zabbix/externalscripts/ or similar paths for custom SMS scripts if defined in media type configuration.
    Affected if SMS-related scripts or external command paths are defined and writable.

You are affected if your Zabbix version is one of the affected versions AND you have an SMS media type enabled with users who can access the SMS testing functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.4.15
Interim mitigation

Implement strict input validation and sanitization for the phone number field, using an allowlist of permitted characters (digits, plus sign, dashes) and rejecting any characters that could be interpreted as AT command separators.

Recommended fix High confidence

Zabbix 5.0.43+, 6.0.31+, 6.4.16+, or 7.0.1+ (select the appropriate branch for your environment)

  1. Review Zabbix release notes for versions 5.0.43, 6.0.31, 6.4.16, and 7.0.1 to understand changes and ensure compatibility
  2. Back up the Zabbix database and configuration files
  3. Schedule a maintenance window for the upgrade
  4. For Zabbix 5.0.x: Upgrade to version 5.0.43 or later
  5. For Zabbix 6.0.x: Upgrade to version 6.0.31 or later
  6. For Zabbix 6.4.x: Upgrade to version 6.4.16 or later
  7. For Zabbix 7.0.x: Upgrade to version 7.0.1 or later
  8. After upgrade, verify SMS media type functionality works correctly with valid phone numbers
Caveat Review release notes for your version branch as minor version upgrades may include database schema changes and new features requiring testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zabbix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22122 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data