dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-27233

MEDIUM · 5.7 CVSS v4.0 Published 2025-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 Agent 2 smartctl plugin does not properly sanitize smart.disk.get parameters, allowing an attacker to inject unexpected arguments into the smartctl command. This can be used to leak the NTLMv2 hash from a Windows system.

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

The Zabbix Agent 2 smartctl plugin fails to sanitize smart.disk.get parameters, allowing injection of arbitrary arguments into the smartctl command. This command injection can be exploited to trigger SMB connections that leak NTLMv2 hashes from Windows systems.

MitigationApply the vendor patch for Zabbix Agent 2 to address parameter sanitization. If immediate patching is not possible, disable the smartctl plugin or restrict access to the smart.disk.get item.

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

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
Adjacent
Complexity
High
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Zabbix Agent 2 is installed
    Run 'zabbix_agent2 --version' or check for the agent2 binary in typical locations like /usr/sbin/zabbix_agent2 or /usr/bin/zabbix_agent2
    Affected if Zabbix Agent 2 binary exists on the system
  2. Identify the Zabbix Agent 2 version
    Execute 'zabbix_agent2 --version' and note the reported version number
    Affected if The installed version falls within any unpatched version range for Zabbix Agent 2 (compare to vendor advisories for CVE-2025-27233)
  3. Verify smartctl plugin is loaded
    Check the agent configuration file (typically zabbix_agent2.conf or included .conf files in /etc/zabbix/zabbix_agent2.d/) for 'Plugins.Smartctl.*' parameters or look for the smartctl plugin binary
    Affected if The smartctl plugin configuration section exists and the plugin is not explicitly disabled
  4. Confirm smart.disk.get item is accessible
    Review Zabbix server/item configuration or agent metrics accessible via 'zabbix_agent2 -p' for 'smart.disk.get' key availability
    Affected if The smart.disk.get item key is exposed and accessible to unauthenticated or low-privilege users
  5. Inspect for suspicious SMB/network activity
    Monitor network connections or review Zabbix logs for unexpected outbound SMB connections to remote hosts, especially after smart.disk.get item invocation
    Affected if Outbound SMB connections are observed to unexpected internal or external hosts following smartctl queries

A user is affected if Zabbix Agent 2 with the smartctl plugin enabled exposes the smart.disk.get item to untrusted users in an environment where Windows systems can be reached via SMB, allowing potential NTLMv2 hash leakage.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for Zabbix Agent 2 to address parameter sanitization. If immediate patching is not possible, disable the smartctl plugin or restrict access to the smart.disk.get item.

Recommended fix Moderate confidence

Upgrade to Zabbix Agent 2 version containing the CVE-2025-27233 fix (check release notes for specific version numbers)

  1. Check Zabbix Agent 2 version via 'zabbix_agent2 --version' or in the Zabbix web interface under 'Latest data' > 'Zabbix server health'
  2. Consult Zabbix release notes at https://www.zabbix.com/rn for version 7.0.x, 6.4.x, and 6.0.x to identify the release containing the fix for CVE-2025-27233
  3. Upgrade Zabbix Agent 2 to the fixed release using the official Zabbix repository or packages
  4. Restart the Zabbix Agent 2 service to apply the update
  5. Verify the smartctl plugin functions correctly post-upgrade by testing smart.disk.get items
Caveat Review Zabbix release notes for any breaking changes between current and target versions, particularly in plugin configurations

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27233 — 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-2025-27233 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