Bug 2040749 (CVE-2022-23131)

Summary:	CVE-2022-23131 zabbix: Unsafe client-side session storage leading to authentication bypass / instance takeover via Zabbix Frontend with configured SAML
Product:	[Other] Security Response	Reporter:	Michael Kaplan <mkaplan>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	bennie.joubert, dan, gwync, ms, orion, volker27
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-14 17:01:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2040750, 2040751, 2040752
Bug Blocks:

Description Michael Kaplan 2022-01-14 16:13:42 UTC

In the case of instances where the SAML SSO authentication is enabled (non-default), session data can be modified by a malicious actor, because a user login stored in the session was not verified. Malicious unauthenticated actor may exploit this issue to escalate privileges and gain admin access to Zabbix Frontend. To perform the attack, SAML authentication is required to be enabled and the actor has to know the username of Zabbix user (or use the guest account, which is disabled by default).

References:

https://support.zabbix.com/browse/ZBX-20350

Comment 1 Michael Kaplan 2022-01-14 16:14:03 UTC

Created zabbix tracking bugs for this issue:

Affects: fedora-all [bug 2040750]


Created zabbix40 tracking bugs for this issue:

Affects: epel-all [bug 2040751]


Created zabbix50 tracking bugs for this issue:

Affects: epel-all [bug 2040752]

Comment 2 Product Security DevOps Team 2022-01-14 17:01:41 UTC

This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.