Command execution via crafted tenant file names
Published Feb 1, 2023 · Updated Mar 26, 2025
Command injection in F5 F5OS-A 1.2.0 to before 1.3.0 and F5OS-C 1.3.0 to before 1.5.0 allows local users to execute commands. The tenant-file processing path passes attacker-controlled file-name content into a command context, but F5 has not disclosed the responsible handler or parsing operation. Exploitation requires local access, user interaction, and high-complexity conditions; injected commands can read or alter appliance data and interrupt service.
Summary
What happened
Command injection in F5 F5OS-A 1.2.0 to before 1.3.0 and F5OS-C 1.3.0 to before 1.5.0 allows local users to execute commands. The tenant-file processing path passes attacker-controlled file-name content into a command context, but F5 has not disclosed the responsible handler or parsing operation. Exploitation requires local access, user interaction, and high-complexity conditions; injected commands can read or alter appliance data and interrupt service.
The record
- CVE
- CVE-2023-22657
- Published
- Feb 1, 2023
- Updated
- Mar 26, 2025
- Vendor
- F5 Networks
- Product
- F5OS-A
- Classifications
- CWE-77, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.0 <1.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo