CVE-2022-41800
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn BIG-IP running Appliance mode, an authenticated Administrator can bypass Appliance mode restrictions through an undisclosed iControl REST endpoint, allowing security boundary crossing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0>= 13.1.0, <= 17.0.0>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BIG-IP versionRun 'tmsh show /sys version' or query iControl REST endpoint GET /mgmt/tm/sys/version to retrieve the installed version.Affected if The version falls within 13.1.0-13.1.5, 14.1.0-14.1.5, 15.1.0-15.1.8, 16.1.0-16.1.3, or 17.0.0.
-
Confirm Appliance mode is activeRun 'tmsh show /sys appliance' or check the system database with 'tmsh list /sys db systemauth.appliance' to see if Appliance mode is enabled.Affected if The output shows Appliance mode is enabled (systemauth.appliance value is 'true').
-
Verify iControl REST is exposedConfirm the iControl REST API is accessible on the management interface or self IP. Check with 'tmsh list /sys httpd' for REST settings.Affected if iControl REST is enabled and accessible.
-
Review admin user activity logsExamine /var/log/audit for iControl REST API calls, particularly POST requests to undocumented endpoints. Use 'grep -i icrtd /var/log/audit' patterns.Affected if Unusual or undocumented iControl REST endpoint calls appear in audit logs from administrator sessions.
You are affected if your BIG-IP version matches the affected ranges AND Appliance mode is enabled, allowing an authenticated admin to potentially exploit the undisclosed REST endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply F5-provided patches for this vulnerability. Until patch availability, strictly limit administrative access and monitor for unusual iControl REST API activity.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41800 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data