Skip to content

In the case of instances where the SAML SSO...

Critical severity Unreviewed Published Jan 14, 2022 to the GitHub Advisory Database • Updated Feb 3, 2023

Package

No package listedSuggest a package

Affected versions

Unknown

Patched versions

Unknown

Description

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

Published by the National Vulnerability Database Jan 13, 2022
Published to the GitHub Advisory Database Jan 14, 2022
Last updated Feb 3, 2023

Severity

Critical

EPSS score

97.173%
(100th percentile)

Weaknesses

CVE ID

CVE-2022-23131

GHSA ID

GHSA-4g73-3mxf-j47w

Source code

No known source code

Dependabot alerts are not supported on this advisory because it does not have a package from a supported ecosystem with an affected and fixed version.

Learn more about GitHub language support

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.