Persistent SSH access via aborted key addition
Published Jun 10, 2025 · Updated Jun 11, 2025
Incomplete cleanup in Fortinet FortiOS and FortiProxy allows local users with VDOM privileges to silently add SSH key files via CLI requests. The CLI fails to remove the SSH key file when a crafted key-add operation is aborted, leaving the key installed despite the failed transaction. VDOM privileges and CLI access are required; the residual key permits later SSH authentication with the matching private key.
Summary
What happened
Incomplete cleanup in Fortinet FortiOS and FortiProxy allows local users with VDOM privileges to silently add SSH key files via CLI requests. The CLI fails to remove the SSH key file when a crafted key-add operation is aborted, leaving the key installed despite the failed transaction. VDOM privileges and CLI access are required; the residual key permits later SSH authentication with the matching private key.
The record
- CVE
- CVE-2023-29184
- Published
- Jun 10, 2025
- Updated
- Jun 11, 2025
- Vendor
- Fortinet
- Product
- FortiOS
- Classifications
- CWE-459, T1098.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 2025CVE publishedPublication date reported by the CVE source.
- Jun 11, 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=6.2.0 <=6.2.17
- Affected versionversion=6.4.0 <=6.4.16
- Affected versionversion=7.0.0 <=7.0.17
- Affected versionversion=7.2.0 <=7.2.11
What conditions does exploitation require?
What is affected?
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