F5os AOperating system · F5
CVE-2023-22657
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 F5OS-A beginning in version 1.2.0 to before 1.3.0 and F5OS-C beginning in version 1.3.0 to before 1.5.0, processing F5OS tenant file names may allow for command injection. 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 confidenceF5OS tenant file name processing contains a command injection vulnerability allowing attackers to inject arbitrary shell commands through unsanitized file name input in affected versions of F5OS-A (1.2.0 to before 1.3.0) and F5OS-C (1.3.0 to before 1.5.0). This is a classic OS command injection flaw where user-controlled file names are passed to system calls without proper sanitization.
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
F5os AOperating system
>= 1.2.0, < 1.3.0
F5os COperating system
>= 1.3.0, < 1.5.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 F5OS product variant and versionLog into the F5OS management interface or CLI and retrieve the system version information using 'show system version' or 'tmsh show /sys version' commands. Determine whether the system is F5OS-A or F5OS-C based on the product model.Affected if The product is F5OS-A with version >= 1.2.0 and < 1.3.0, OR F5OS-C with version >= 1.3.0 and < 1.5.0
-
Confirm tenant file import functionality is accessibleDetermine whether the tenant import or file upload feature is enabled on the F5OS system. This is typically accessible through the web UI under Tenant Management or via the CLI command 'tmsh list /ltm virtual' to check for tenant-related configurations.Affected if Tenant file import operations are permitted and the system accepts file names from users or processes tenant archives
-
Check for suspicious tenant file names or recent file importsReview system logs and audit trails for tenant import events. Use 'ls -la /var/log/' or the F5OS audit log interface to examine recent tenant import operations. Look for file names containing shell metacharacters like ; & | $ ` or unusual patterns.Affected if Tenant import operations show file names with special characters that could indicate injection attempts, or unexpected tenant imports were performed
-
Inspect network accessibility to the management interfaceVerify the network exposure of the F5OS management interface. Check if it is directly accessible from untrusted networks using 'show /net self-allow' or review the management IP configuration and access lists.Affected if The management interface is exposed to the internet or untrusted networks without restrictive ACLs
The environment is affected if the installed F5OS version falls within the vulnerable ranges (F5OS-A 1.2.0 to <1.3.0 or F5OS-C 1.3.0 to <1.5.0) and the tenant file import feature is accessible, particularly if the management interface is network-accessible.
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 · scoped1.3.01.5.0
Upgrade F5OS-A to version 1.3.0 or later and F5OS-C to version 1.5.0 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the F5OS management interface and implement compensating controls such as input validation at upstream layers.
F5OS-A: 1.3.0 or later; F5OS-C: 1.5.0 or later
- 1. Identify the F5OS platform type (A or C) using the system management interface or CLI.
- 2. For F5OS-A: Upgrade to version 1.3.0 or later from the F5 downloads portal.
- 3. For F5OS-C: Upgrade to version 1.5.0 or later from the F5 downloads portal.
- 4. Before upgrading, back up current configuration following F5 backup procedures.
- 5. Apply the upgrade via the F5OS management interface or tmsh command line.
- 6. After upgrade, verify the system is operational and the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in F5os A
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22657 — 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-22657 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