dbcve.org
Debian LinuxOperating system · Debian

CVE-2020-11800

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-07
Fix available
A fix is available. Upgrade to 3.0.31 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Server 2.2.x and 3.0.x before 3.0.31, and 3.2 allows remote attackers to execute arbitrary code.

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 · moderate confidence

CVE-2020-11800 is a critical remote code execution vulnerability in Zabbix Server versions 2.2.x, 3.0.x before 3.0.31, and 3.2. The vulnerability allows unauthenticated remote attackers to execute arbitrary code on the Zabbix server by exploiting improper input validation or authentication mechanisms in the Server's web interface or API, likely through specially crafted requests that bypass security controls.

MitigationUpgrade Zabbix Server to version 3.0.31 or later, or migrate to a supported version (4.x or newer). If immediate patching is not possible, restrict network access to the Zabbix web interface and API to trusted IPs only, and disable any unused authentication methods.

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
Debian LinuxOperating system
Affected:= 9.0
ZabbixApplication
Affected:>= 2.2.0, < 3.0.31= 3.2.0
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1= 15.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify Zabbix Server version
    Run 'zabbix_server -V' or check the package manager output (dpkg -l | grep zabbix, rpm -qi zabbix-server)
    Affected if Version is 2.2.x, 3.0.x before 3.0.31, or exactly 3.2.0
  2. Verify web interface is enabled
    Check if Zabbix frontend is installed and running - look for /usr/share/zabbix or /var/www/html/zabbix directories, or check if Apache/Nginx is serving Zabbix pages
    Affected if The Zabbix web frontend is installed and accessible on the network
  3. Confirm network exposure of web interface
    Check listening ports (netstat -tlnp | grep -E '80|443|10050|10051') and review firewall rules or reverse proxy configuration
    Affected if The Zabbix web interface is exposed to untrusted networks without IP restrictions
  4. Check authentication configuration
    Inspect /etc/zabbix/web/zabbix.conf.php for authentication settings and review PAM/LDAP integration if used
    Affected if Using default authentication with the web interface exposed to the network

You are affected if Zabbix Server version is 2.2.x, 3.0.x before 3.0.31, or 3.2.0 AND the web interface/API is network-accessible to untrusted hosts.

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 3.0.31 or later
Fixed in 3.0.31
Interim mitigation

Upgrade Zabbix Server to version 3.0.31 or later, or migrate to a supported version (4.x or newer). If immediate patching is not possible, restrict network access to the Zabbix web interface and API to trusted IPs only, and disable any unused authentication methods.

Recommended fix Moderate confidence

Zabbix 3.0.31 or later (or migrate to supported 4.0 LTS/5.0 LTS branch)

  1. Identify the Zabbix Server version currently installed (e.g., zabbix-server-mysql, zabbix-server-pgsql)
  2. Stop the Zabbix Server service (systemctl stop zabbix-server or equivalent)
  3. Back up the existing Zabbix database and configuration files
  4. Update the package repository and upgrade the Zabbix Server package to version 3.0.31 or later (or to 4.0 LTS/5.0 LTS for 3.2.x branches)
  5. Review and update configuration files if necessary (zabbix_server.conf)
  6. Start the Zabbix Server service
  7. Verify the running version matches the expected fixed release (zabbix_server -V)
  8. Test that Zabbix frontend connects to the server and monitoring functions work
Caveat Database schema upgrades may be required when upgrading between major Zabbix versions; review upgrade documentation and test in non-production first

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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