dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-23132

HIGH · 7.3 CVSS v3.1 Published 2022-01-13
Fix available
A fix is available. Upgrade to after 5.4.8 or later.
See remediation →
82/100
Remediation priority · High
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
During Zabbix installation from RPM, DAC_OVERRIDE SELinux capability is in use to access PID files in [/var/run/zabbix] folder. In this case, Zabbix Proxy or Server processes can bypass file read, write and execute permissions check on the file system level

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
How this class of weakness works · CWE-284

The application fails to correctly restrict what a user can do or reach, so functions or resources are available to people who should not have them. Attackers simply probe for the paths where the check is missing or wrong. The fix is to enforce access-control decisions consistently on every request, evaluated against the acting user rather than assumed from context.

General guidance for the improper access control class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
ZabbixApplication
Affected:>= 4.0.0, <= 4.0.36>= 5.0.0, <= 5.0.18>= 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
Low
Integrity
Low
Availability
Low

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

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 →
Recommended fix Moderate confidence

Zabbix 4.0.37+, 5.0.19+, 5.4.9+, or 6.0.1+ (or latest stable 6.x LTS)

  1. 1. Identify the currently installed Zabbix version using: `zabbix_server --version` or `zabbix_proxy --version`
  2. 2. For Zabbix 4.0.x: upgrade to version 4.0.37 or later
  3. 3. For Zabbix 5.0.x: upgrade to version 5.0.19 or later
  4. 4. For Zabbix 5.4.x: upgrade to version 5.4.9 or later
  5. 5. For Zabbix 6.0.x: upgrade to version 6.0.1 or later
  6. 6. On Fedora systems: run `dnf update zabbix*` to apply the latest available package
  7. 7. After upgrade, verify SELinux context is correctly applied: `ls -la /var/run/zabbix/`
  8. 8. Restart Zabbix services: `systemctl restart zabbix-server` or `systemctl restart zabbix-proxy`
Caveat Review Zabbix release notes for any breaking changes between your current version and the target version before upgrading

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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