# CVE-2022-43515: X-Forwarded-For header is active by default causes access to Zabbix sites in maintenance mode

> Attackers can bypass maintenance mode IP restrictions by spoofing the X-Forwarded-For header, gaining unauthorized access to the Zabbix Frontend.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2022
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-43515, GHSA-hh7f-cch9-52mr, SUSE-SU-2022:4477-1, UBUNTU-CVE-2022-43515

## What is CVE-2022-43515?

CVE-2022-43515 is a medium-severity authentication bypass vulnerability in Zabbix Frontend, published on 12 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zabbix Frontend provides a feature that allows admins to maintain the installation and ensure that only certain IP addresses can access it. In this way, any user will not be able to access the Zabbix Frontend while it is being maintained and possible sensitive data will be prevented from being disclosed. An attacker can bypass this protection and access the instance using IP address not listed in the defined range.

Weakness: CWE-863 (Incorrect Authorization), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-43515?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zabbix` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 4.0.12-4.21.1 |
| `zabbix` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 4.0.12-4.21.1 |
| `zabbix` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.0.12-4.21.1 |
| `zabbix` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 4.0.12-4.21.1 |
| `zabbix` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.0.12-4.21.1 |
| `zabbix` | SUSE:OpenStack Cloud 9 | All versions | 4.0.12-4.21.1 |
| `zabbix` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 4.0.12-4.21.1 |

Products: Zabbix Frontend.

## How do I fix CVE-2022-43515?

Apply the vendor's patch.

## Is CVE-2022-43515 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43515 exists.

## Other vulnerabilities in Zabbix Frontend

- [CVE-2023-32725](https://insights.sbomify.com/CVE-2023-32725/): Leak of zbx_session cookie when using a scheduled report that includes a dashboard with a URL widget. (critical 9.6)
- [CVE-2025-27232](https://insights.sbomify.com/CVE-2025-27232/): Frontend arbitrary file read in oauth.authorize action (medium 6.8)
- [CVE-2023-29457](https://insights.sbomify.com/CVE-2023-29457/): Insufficient validation of Action form input fields (medium 6.3)
- [CVE-2025-49643](https://insights.sbomify.com/CVE-2025-49643/): Frontend DoS vulnerability due to asymmetric resource consumption (medium 6.0)
- [CVE-2023-29456](https://insights.sbomify.com/CVE-2023-29456/): Inefficient URL schema validation (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43515 and fix it if it is affected.

What it is: CVE-2022-43515 is a medium-severity authentication bypass vulnerability in Zabbix Frontend, published on 12 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43515 exists.

Affected product: Zabbix Frontend. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-43515/ (Markdown: https://insights.sbomify.com/CVE-2022-43515/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-43515
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-43515
- OSV: https://osv.dev/vulnerability/CVE-2022-43515

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-43515/
Summaries are generated and may contain mistakes; the official description above is the record.