Unauthenticated brute-force exposure via unlogged failed logins
Published Dec 6, 2022 · Updated Oct 22, 2024
Insufficient logging in FortiSandbox and FortiDeceptor allows remote attackers to brute-force credentials without audit entries. The authentication path neither records failed logins nor limits repeated attempts across the affected releases, leaving password guessing without an audit trail. Network access to a management login is sufficient; successful guessing still requires a valid password, and no direct data alteration or service interruption is reported.
Summary
What happened
Insufficient logging in FortiSandbox and FortiDeceptor allows remote attackers to brute-force credentials without audit entries. The authentication path neither records failed logins nor limits repeated attempts across the affected releases, leaving password guessing without an audit trail. Network access to a management login is sufficient; successful guessing still requires a valid password, and no direct data alteration or service interruption is reported.
The record
- CVE
- CVE-2022-30305
- Published
- Dec 6, 2022
- Updated
- Oct 22, 2024
- Vendor
- Fortinet
- Product
- FortiSandbox
- Classifications
- CWE-778, CWE-307, CAPEC-112, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2022CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=3.1.0 <=3.1.5
- Affected versionversion=3.2.0 <=3.2.3
- Affected versionversion=4.0.0 <=4.0.2
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