dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 8 Mar 2022.
FedoraOperating system · Fedoraproject

CVE-2022-23134

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-13
Fix available
A fix is available. Upgrade to after 5.4.8 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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
After the initial setup process, some steps of setup.php file are reachable not only by super-administrators, but by unauthenticated users as well. Malicious actor can pass step checks and potentially change the configuration of Zabbix Frontend.

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 Frontend contains an access control vulnerability in setup.php where certain configuration steps remain accessible to unauthenticated users after initial setup completion. Attackers can bypass step verification checks to access configuration pages intended only for super-administrators, potentially allowing modification of frontend settings.

MitigationRestrict access to setup.php steps to authenticated super-administrators only, or ensure the setup process properly terminates all access upon completion. Consider disabling or removing the setup.php file after initial configuration.

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
FedoraOperating system
Affected:= 34= 35
Debian LinuxOperating system
Affected:= 9.0
ZabbixApplication
Affected:>= 5.4.0, <= 5.4.8= 6.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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 Frontend installation
    Locate Zabbix Frontend files. Common paths include /usr/share/zabbix/, /var/www/html/zabbix/, or check your web server document root for 'setup.php' and 'index.php' files.
    Affected if Zabbix Frontend is installed on the system.
  2. Check installed Zabbix version
    Find the version file. In Zabbix Frontend installations, check include/version.php or similar version definition files for the installed version number.
    Affected if The installed version falls within 5.4.0 to 5.4.8, equals 6.0.0, or is an unspecified version derived from affected Fedora/Debian packages (Fedora 34/35, Debian 9.0).
  3. Verify setup.php is accessible
    Attempt to access the setup.php file via HTTP/HTTPS request to the Zabbix web interface, for example: GET /zabbix/setup.php
    Affected if The setup.php file returns a response rather than a 404 or 403 error.
  4. Confirm setup has been completed
    Check if the Zabbix configuration file (zabbix.conf.php or similar) exists in the include/ directory, indicating initial setup was completed.
    Affected if Initial setup was completed (configuration file exists) but setup.php remains accessible to unauthenticated users.
  5. Test unauthenticated access to setup steps
    Send requests to setup.php with various step parameters (such as ?step=1, ?step=2, or similar) without providing authentication credentials.
    Affected if Setup configuration steps are reachable without authentication after initial setup is complete.

A system is affected if it runs Zabbix Frontend versions 5.4.0-5.4.8 or 6.0.0, the setup.php file is web-accessible, initial setup has been completed, and unauthenticated users can access setup configuration steps.

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 5.4.8
Vendor patch support.zabbix.com →
Interim mitigation

Restrict access to setup.php steps to authenticated super-administrators only, or ensure the setup process properly terminates all access upon completion. Consider disabling or removing the setup.php file after initial configuration.

Recommended fix High confidence

Zabbix 5.4.9 or later / Zabbix 6.0.1 or later (or latest stable 6.x release)

  1. 1. Backup your current Zabbix database and configuration files before upgrading
  2. 2. For Debian/Fedora systems: update your package repository and upgrade the Zabbix packages using your package manager (apt-get upgrade or dnf update)
  3. 3. For Zabbix 5.4.x: upgrade to Zabbix 5.4.9 or later
  4. 4. For Zabbix 6.0.x: upgrade to Zabbix 6.0.1 or later
  5. 5. After upgrade, verify that the setup.php file is properly protected and only accessible during initial installation
  6. 6. Review Zabbix frontend configuration to ensure no unauthorized changes were made
  7. 7. Restart Zabbix services if required by the upgrade
Caveat Standard upgrade precautions apply - test in staging first, backup database, review release notes for any configuration changes

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

Fix this in Fedora Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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