# CVE-2022-41622: iControl SOAP vulnerability

> Attackers can perform cross-site request forgery attacks via iControl SOAP on F5 BIG-IP and BIG-IQ devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-3wmp-g7x5-v6hv

## What is CVE-2022-41622?

CVE-2022-41622 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In all versions, 

BIG-IP and BIG-IQ are vulnerable to cross-site request forgery (CSRF) attacks through iControl SOAP.  

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 12 products.


Products: F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Domain Name System, F5 Big-Ip Fraud Protection Service, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Iq Centralized Management.

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

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

## Is CVE-2022-41622 being exploited?

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

Public exploit code:

- A PoC exploit for CVE-2022-41622 - a CSRF in F5 BIG-IP control plane that leads to remote root (github_poc): https://github.com/rbowes-r7/refreshing-soap-exploit
- F5 BIG-IP iControl CSRF File Write SOAP API (metasploit)

## Other vulnerabilities in F5 Big-Ip Access Policy Manager

- [CVE-2023-46747](https://insights.sbomify.com/CVE-2023-46747/): F5 BIG-IP Configuration Utility Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-1388](https://insights.sbomify.com/CVE-2022-1388/): F5 BIG-IP Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-22986](https://insights.sbomify.com/CVE-2021-22986/): F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-22991](https://insights.sbomify.com/CVE-2021-22991/): F5 BIG-IP Traffic Management Microkernel Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2020-5902](https://insights.sbomify.com/CVE-2020-5902/): F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41622 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41622 exists.

Affected product: F5 Big-Ip Access Policy Manager. 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-41622/ (Markdown: https://insights.sbomify.com/CVE-2022-41622/index.md)
```

## Sources

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

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