CVE-2021-23043
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 · uneditedOn BIG-IP, on all versions of 16.1.x, 16.0.x, 15.1.x, 14.1.x, 13.1.x, 12.1.x, and 11.6.x, a directory traversal vulnerability exists in an undisclosed page of the BIG-IP Configuration utility that allows an attacker to access arbitrary files. 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 · high confidenceA directory traversal vulnerability in the BIG-IP Configuration utility allows authenticated attackers to access arbitrary files on the filesystem by manipulating path traversal sequences in an undisclosed page.
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>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed BIG-IP versionRun command 'tmsh show /sys version' on the BIG-IP command line, or check System > Software Management > Image in the GUI, or query the REST API endpoint https://<host>/mgmt/tm/sys/versionAffected if The installed version falls within any of these ranges: 11.6.0-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4, 15.1.0-15.1.3, or 16.0.0-16.1.0
-
Determine which modules are provisionedRun 'tmsh list sys provision' or check System > Resource Provisioning in the GUI to see which modules (APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM) are provisioned on the systemAffected if Any of the affected modules (APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM) are provisioned and the version is within the affected ranges
-
Verify Configuration utility accessibilityCheck if the BIG-IP Configuration utility (web-based management interface) is exposed to untrusted networks. Review network access settings in Network > Self IP or check the management interface configuration via 'tmsh list sys management-ip'Affected if The Configuration utility is accessible from untrusted networks (not restricted to trusted IP ranges)
-
Confirm authentication statusReview whether the undisclosed page used in the attack requires authentication. Typically, the Configuration utility requires login, but verify that authentication is enforced for all management interfacesAffected if An attacker can authenticate to the Configuration utility (even with low-privilege user access)
You are affected if your BIG-IP system runs a version within the listed ranges AND has any of the affected modules provisioned AND the Configuration utility is accessible to an authenticated user.
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.
dbcve · scopedApply the appropriate F5 security patch for this vulnerability. Until patched, restrict access to the BIG-IP Configuration utility to trusted networks or IP addresses.
Big-IP 14.1.5 or later (or latest stable 15.1.x/16.0.x/16.1.x release)
- 1. Identify the current Big-IP version by running 'tmsh show sys version' on the command line
- 2. Determine which Big-IP module(s) (APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM) are in use as all are affected
- 3. Schedule a maintenance window for the upgrade
- 4. Backup the current Big-IP configuration using 'tmsh save sys config'
- 5. Download the appropriate fixed version from the F5 downloads portal (support.f5.com)
- 6. For version 14.1.x, upgrade to 14.1.5 or later
- 7. For version 13.1.x, upgrade to 13.1.5 or later
- 8. For version 12.1.x, upgrade to 12.1.7 or later (if supported)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23043 — 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-2021-23043 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