CVE-2022-41800 in the critical feed json
Appliance mode iControl REST vulnerability
published 3y ago modified 4mo ago also EUVD-2022-44968
- cvss
- 8.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 76.9%
- EPSS 76.9% chance of exploitation in 30 days, percentile 99.5%
- public exploits
- 1
- Metasploit, plus a Nuclei check
Summary
In all versions of BIG-IP, when running in Appliance mode, an authenticated user assigned the Administrator role may be able to bypass Appliance mode restrictions, utilizing an undisclosed iControl REST endpoint. A successful exploit can allow the attacker to cross a security boundary.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Is CVE-2022-41800 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/linux/http/f5_icontrol_rpmspec_rce_cve_2022_41800)
- Published
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
76.87% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/http/f5_icontrol_rpmspec_rce_cve_2022_41800 F5 BIG-IP iControl Authenticated RCE via RPM Creator metasploit exploit, excellent rank, 2022-11-16
- Nuclei template F5 BIG-IP Appliance Mode - Command Injection nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N |
Affected products
- F5 BIG-IP
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
-
support.f5.com
/csp/article/K13325942
vendor-advisory
Sources
- CVE List CVE-2022-41800
- NVD CVE-2022-41800
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.