Version disclosure via unauthenticated JavaScript file
Published Jan 5, 2022 · Updated Oct 25, 2024
Information disclosure in Fortinet FortiMail 6.0.9 and earlier, 6.2.4 and earlier, or 6.4.1 and earlier exposes version data to remote attackers. The unauthenticated GUI serves a JavaScript file containing the software version, placing the value in client-side resources before login. Any remote party that can reach the GUI can identify the release and use that information to target version-specific weaknesses; no configuration change or service interruption is reported.
Summary
What happened
Information disclosure in Fortinet FortiMail 6.0.9 and earlier, 6.2.4 and earlier, or 6.4.1 and earlier exposes version data to remote attackers. The unauthenticated GUI serves a JavaScript file containing the software version, placing the value in client-side resources before login. Any remote party that can reach the GUI can identify the release and use that information to target version-specific weaknesses; no configuration change or service interruption is reported.
The record
- CVE
- CVE-2020-15933
- Published
- Jan 5, 2022
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiMail
- Classifications
- CWE-497, CWE-200, T1592.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 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=FortiMail 6.4.1, 6.4.0, 6.2.4, 6.2.3, 6.2.2, 6.2.1, 6.2.0, 6.0.9, 6.0.8, 6.0.7, 6.0.6, 6.0.5, 6.0.4, 6.0.3, 6.0.2, 6.0.1, 6.0.0, 5.4.12, 5.4.11, 5.4.10, 5.4.9, 5.4.8, 5.4.7, 5.4.6, 5.4.5, 5.4.4, 5.4.3, 5.4.2, 5.4.1, 5.4.0, 5.3.13, 5.3.12, 5.3.10, 5.3.9, 5.3.8, 5.3.7, 5.3.6, 5.3.5, 5.3.4, 5.3.3, 5.3.2, 5.3.1, 5.3.0, 5.2.10, 5.2.9, 5.2.8, 5.2.7, 5.2.6, 5.2.5, 5.2.4, 5.2.3, 5.2.2, 5.2.1, 5.2.0, 5.1.7, 5.1.6, 5.1.5, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, 5.0.11, 5.0.10, 5.0.9, 5.0.8, 5.0.7, 5.0.6, 5.0.5, 5.0.4, 5.0.3, 5.0.2, 5.0.1, 5.0.0, 4.3.9, 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2, 4.3.1, 4.3.0, 4.2.4, 4.2.3, 4.2.2, 4.2.1, 4.2.0, 4.1.3, 4.1.2, 4.1.1, 4.1.0, 4.0.5, 4.0.4, 4.0.3, 4.0.1
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