Privileged code execution via arbitrary memory writes
Published Dec 13, 2021 · Updated Oct 25, 2024
Hidden debug functionality in Fortinet FortiOS 7.0.0, 6.4.6, and 6.2.9 allows local users to execute unauthorized code or commands. The CLI chains print str and cmd mem debug commands to read hexadecimal values from, or write them to, any memory address. Exploitation requires a highly privileged local session; arbitrary reads expose memory, while writes enable code or command execution.
Summary
What happened
Hidden debug functionality in Fortinet FortiOS 7.0.0, 6.4.6, and 6.2.9 allows local users to execute unauthorized code or commands. The CLI chains print str and cmd mem debug commands to read hexadecimal values from, or write them to, any memory address. Exploitation requires a highly privileged local session; arbitrary reads expose memory, while writes enable code or command execution.
The record
- CVE
- CVE-2021-36169
- Published
- Dec 13, 2021
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiOS
- Classifications
- T1059
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 13, 2021CVE publishedPublication date reported by the CVE source.
- Oct 25, 2024Record 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=FortiOS 7.0.0, 6.4.6, 6.2.9
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