Endpoint protection removal via hard-coded registration key
Published Apr 6, 2022 · Updated Oct 25, 2024
Hard-coded key use in Fortinet FortiEDR Collector 4.0.0 and 5.0.0 through 5.0.2 allows local users to disable or uninstall collectors. The registration mechanism relies on a fixed cryptographic key embedded in the collector instead of a deployment-specific secret. Low-privileged local access within the same deployment is sufficient, and successful exploitation removes endpoint monitoring and response.
Summary
What happened
Hard-coded key use in Fortinet FortiEDR Collector 4.0.0 and 5.0.0 through 5.0.2 allows local users to disable or uninstall collectors. The registration mechanism relies on a fixed cryptographic key embedded in the collector instead of a deployment-specific secret. Low-privileged local access within the same deployment is sufficient, and successful exploitation removes endpoint monitoring and response.
The record
- CVE
- CVE-2022-23440
- Published
- Apr 6, 2022
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiEDR
- Classifications
- CWE-798, CWE-321, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 6, 2022CVE 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=FortiEDR 5.0.2, 5.0.1, 5.0.0, 4.0.0
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