# CVE-2022-43516: Zabbix Agent installer adds “allow all TCP any any” firewall rule

> The Zabbix agent installer creates an overly permissive Windows Firewall rule, allowing unrestricted incoming TCP connections to all programs and ports.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2022
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-wpfh-pv35-c3gc

## What is CVE-2022-43516?

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

### Official description

A Firewall Rule which allows all incoming TCP connections to all programs from any source and to all ports is created in Windows Firewall after Zabbix agent installation (MSI)

Weakness: CWE-16

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

It affects 2 products.


Products: Microsoft Windows Firewall, Zabbix Zabbix.

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

No fix has been published for CVE-2022-43516 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-43516 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43516 is a medium-severity vulnerability in Zabbix Zabbix, 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-43516 exists.

Affected product: Zabbix Zabbix. 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-43516/ (Markdown: https://insights.sbomify.com/CVE-2022-43516/index.md)
```

## Sources

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

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