CVE-2023-23552
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 versions 17.0.x before 17.0.0.2, 16.1.x before 16.1.3.3, 15.1.0 before 15.1.8, 14.1.x before 14.1.5.3, and all versions of 13.1.x, when a BIG-IP Advanced WAF or BIG-IP ASM security policy is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization. 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 confidenceA denial-of-service vulnerability exists in F5 BIG-IP Advanced WAF and ASM when security policies are configured on virtual servers. Undisclosed requests can cause excessive memory utilization, potentially leading to resource exhaustion and service unavailability.
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.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 BIG-IP versionRun `tmsh show sys version` or check `/etc/product_version` on the BIG-IP systemAffected if The installed version falls within any of these ranges: 13.1.0-13.1.5, 14.1.0-14.1.5.2, 15.1.0-15.1.7, 16.1.0-16.1.3.2, or 17.0.0-17.0.0.1
-
Verify AWF or ASM module is provisionedRun `tmsh list sys provision` and look for 'asm' or 'awaf' (Advanced WAF) entries with a provisioning level other than 'none'Affected if Either ASM or Advanced WAF module is provisioned on the device
-
Confirm security policies exist on virtual serversRun `tmsh list security policy` to list all configured security policies, then cross-reference with virtual servers using `tmsh list ltm virtual` to see which virtual servers reference a security policyAffected if Any virtual server has a security policy assigned (the 'security-policy' option is configured)
You are affected if your BIG-IP runs a vulnerable version (13.1.x, 14.1.0-14.1.5.2, 15.1.0-15.1.7, 16.1.0-16.1.3.2, or 17.0.0-17.0.0.1) AND has Advanced WAF or ASM provisioned AND has security policies configured on virtual servers.
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 · scoped14.1.5.315.1.816.1.3.3
Upgrade BIG-IP to version 17.0.0.2 or later (17.x), 16.1.3.3 or later (16.1.x), 15.1.8 or later (15.1.x), or 14.1.5.3 or later (14.1.x). Note that 13.1.x is affected with no fix available.
Upgrade to the latest version in your current branch: 14.1.5.3+ for 14.1.x, 15.1.8+ for 15.1.x, 16.1.3.3+ for 16.1.x, or 17.0.0.2+ for 17.0.x. For 13.1.x (EoTS), migrate to a supported version branch.
- 1. Identify the current BIG-IP version running Advanced WAF (AWAF) or Application Security Manager (ASM)
- 2. Determine which version branch (13.1.x, 14.1.x, 15.1.x, 16.1.x, or 17.0.x) is currently in use
- 3. For 13.1.x: This version is listed as 'all versions affected' with no fix; plan migration to a supported version (14.1.5.3+, 15.1.8+, 16.1.3.3+, or 17.0.0.2+)
- 4. For 14.1.x: Upgrade to version 14.1.5.3 or later
- 5. For 15.1.x: Upgrade to version 15.1.8 or later
- 6. For 16.1.x: Upgrade to version 16.1.3.3 or later
- 7. For 17.0.x: Upgrade to version 17.0.0.2 or later
- 8. Before upgrading, review the F5 knowledge base for upgrade procedures and ensure proper backups are in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23552 — 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-2023-23552 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