Vulnerability

CVE-2022-23134

Low· 3.7KEVCVSS3.7EPSS93%

.rules3/5

Zabbix Frontend Improper Access Control Vulnerability

Malicious actors can pass step checks and potentially change the configuration of Zabbix Frontend.

Threat signal

61/100

Elevated

Severity

low

CVSS

3.7

EPSS

93%

Active

KEV

CISA KEV — actively exploited

1558d overdue

AffectedZabbix — Frontend

Added to KEV

2022-02-22

Federal patch due (BOD 22-01)

2022-03-08

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2022-23134

CISA description: “Malicious actors can pass step checks and potentially change the configuration of Zabbix Frontend.”

CVSS

v3.1Open in FIRST calculator →

3.7/ 10LOWCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityHighRequires conditions outside attacker's control (race, brute-force, configuration
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactNoneNo confidentiality impact.
Integrity ImpactLowSome data modification; attacker doesn't fully control extent.
Availability ImpactNoneNo availability impact.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

92.6%

probability of exploitation in next 30 days

p100

higher than 100% of all CVEs

3-day trend↑ 0pp

Statistically about to be weaponized — top-tier triage urgency.

Vendor VEX

No VEX statements published for CVE-2022-23134. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAttend

Active exploitation with limited impact — coordinate patching

exploitation: active
automatable: no
impact: partial
mission: support

Lifecycle

2022-02-22Added to CISA KEVransomware: Unknown
2022-02-22Published
2022-03-08Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.