CVE-2021-23025
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 version 15.1.x before 15.1.0.5, 14.1.x before 14.1.3.1, 13.1.x before 13.1.3.5, and all versions of 12.1.x and 11.6.x, an authenticated remote command execution vulnerability exists in the BIG-IP Configuration utility. 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 confidenceThis is an authenticated remote command execution vulnerability in the F5 BIG-IP Configuration utility affecting multiple version branches (15.1.x before 15.1.0.5, 14.1.x before 14.1.3.1, 13.1.x before 13.1.3.5, and all 12.1.x/11.6.x versions). An attacker with valid admin credentials to the Configuration utility can execute arbitrary commands on the underlying system with elevated privileges.
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.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0.5CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the BIG-IP base versionRun `tmsh show /sys version` on the command line, or log into the Configuration utility and check System > About > VersionAffected if The version displayed is 15.1.x before 15.1.0.5, 14.1.x before 14.1.3.1, 13.1.x before 13.1.3.5, or any 12.1.x or 11.6.x version (including 11.6.1-11.6.5)
-
Determine which modules are installedRun `tmsh list /sys module` to list installed modules such as APM, AFM, ASM, Analytics, AAM, DNS, or DDoS Hybrid DefenderAffected if Any of these modules are installed on an affected version (the base version check above determines vulnerability, not the presence of specific modules)
-
Verify Configuration utility accessibilityConfirm whether the Configuration utility web interface (typically on port 443 or 8443) is reachable from network locations where untrusted users could connectAffected if The Configuration utility is exposed to untrusted networks without appropriate access restrictions (this is a prerequisite for remote exploitation)
-
Check for admin user accountsReview user accounts with administrative privileges using `tmsh list /auth user` or via the Configuration utility under User Management > User ListAffected if There are admin-level accounts whose credentials could be compromised (an attacker needs valid admin credentials to exploit this vulnerability)
You are affected if your BIG-IP version falls within the vulnerable ranges (15.1.x < 15.1.0.5, 14.1.x < 14.1.3.1, 13.1.x < 13.1.3.5, or any 12.1.x/11.6.x) AND the Configuration utility is accessible to an attacker who could obtain admin credentials.
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 · scoped13.1.3.514.1.3.115.1.0.5
Apply the vendor-supplied patches to upgrade to version 15.1.0.5 or later, 14.1.3.1 or later, or 13.1.3.5 or later. For EoTS versions (12.1.x, 11.6.x), immediate upgrade to a supported version is required.
14.1.3.1 (or later 14.1.x) | 13.1.3.5 (or later 13.1.x) | 15.1.0.5 (or later 15.1.x)
- 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the Configuration utility (System > Software > Image List)
- 2. Download the appropriate fixed version from F5 Networks (14.1.3.1 or later for 14.1.x, 13.1.3.5 or later for 13.1.x, 15.1.0.5 or later for 15.1.x)
- 3. Upload the ISO image to the BIG-IP device via the Configuration utility (System > Software > Image List > Import) or via SCP/tftp
- 4. Create a boot partition for the new version (System > Software > Volume List > Create)
- 5. Install the new version to the boot partition (System > Software > Volume List > Install)
- 6. Select the new volume as the active boot location and reboot the device
- 7. After reboot, verify the new version is running: 'tmsh show sys version'
- 8. Test critical BIG-IP functionality to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23025 — 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-23025 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