# CVE-2022-26071: Security feature bypass in BIG-IP

> An attacker can bypass UDP source port randomization to scan open ports on F5 BIG-IP devices, undermining network security controls.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6rjr-wmhf-5x38

## What is CVE-2022-26071?

CVE-2022-26071 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 5 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On F5 BIG-IP 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, 13.1.x versions prior to 13.1.5, and all versions of 12.1.x and 11.6.x, a flaw in the way reply ICMP packets are limited in the Traffic Management Microkernel (TMM) allows an attacker to quickly scan open UDP ports. This flaw allows an off-path remote attacker to effectively bypass source port UDP randomization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 11 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.

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

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

## Is CVE-2022-26071 being exploited?

There is no known exploitation of CVE-2022-26071 in the wild and no public exploit code.

## 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-26071 and fix it if it is affected.

What it is: CVE-2022-26071 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 5 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26071 in the wild and no public exploit code.

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

## Sources

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

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