CVE-2023-22374
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 · uneditedA format string vulnerability exists in iControl SOAP that allows an authenticated attacker to crash the iControl SOAP CGI process or, potentially execute arbitrary code. In appliance mode BIG-IP, a successful exploit of this vulnerability 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 confidenceA format string vulnerability exists in F5 BIG-IP iControl SOAP that allows an authenticated attacker to crash the iControl SOAP CGI process or potentially execute arbitrary code through specially crafted format string specifiers in user input.
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>= 14.1.4.6, <= 14.1.5>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.5= 17.0.0>= 14.1.4.6, <= 14.1.5>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.5= 17.0.0>= 14.1.4.6, <= 14.1.5>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.5= 17.0.0>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.5= 17.0.0>= 14.1.4.6, <= 14.1.5>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.0= 17.0.0>= 14.1.4.6, <= 14.1.5>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.5>= 14.1.4.6, <= 14.1.5>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 17.0.0>= 15.1.5.1, <= 15.1.8>= 16.1.2.2, <= 16.1.3= 13.1.5= 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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.
-
Determine BIG-IP versionRun 'tmsh show sys version' on the command line or check the web UI under System > Software Management > Installed VersionsAffected if The version output matches any of these ranges: 14.1.4.6-14.1.5, 15.1.5.1-15.1.8, 16.1.2.2-16.1.3, 13.1.5, or 17.0.0 for your deployed modules
-
Identify deployed BIG-IP modulesRun 'tmsh list sys module' to list all installed module licenses, or check System > Resource > Modules in the web UIAffected if Any of these modules are licensed and running: Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, Ddos Hybrid Defender, Domain Name System, or Fraud Protection Service
-
Verify iControl SOAP is accessibleCheck if port 443 or 8443 responds to iControl SOAP requests, or review System > Configuration > Device > SOAP in the web UI to confirm the service is enabledAffected if iControl SOAP interface is enabled and reachable on the network
-
Confirm authentication methodReview access logs for iControl SOAP endpoint /iControl/iControl.cgi and check authentication configuration in Access Policy Manager if deployedAffected if iControl SOAP accepts authenticated user sessions, as the flaw requires an authenticated attacker
You are affected if your BIG-IP version falls within the listed ranges AND iControl SOAP is enabled with authenticated user access.
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 the vendor-supplied patch for CVE-2023-22374 when available; until then, restrict access to iControl SOAP interfaces to only trusted authenticated users and monitor for signs of exploitation.
- Consultation3.0 h
- Implementation4.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22374 — 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-22374 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