Service interruption via Webmail login memory leak
Published Jul 12, 2021 · Updated Oct 25, 2024
Memory leak in Fortinet FortiMail Webmail 6.4.0 through 6.4.4 and 6.2.0 through 6.2.6 allows remote attackers to interrupt service. The Webmail login-request path fails to release allocated memory after processing specifically crafted unauthenticated requests, allowing repeated requests to consume available memory. No credentials or user interaction are required; the documented consequence is memory exhaustion and denial of service, not data disclosure or modification.
Summary
What happened
Memory leak in Fortinet FortiMail Webmail 6.4.0 through 6.4.4 and 6.2.0 through 6.2.6 allows remote attackers to interrupt service. The Webmail login-request path fails to release allocated memory after processing specifically crafted unauthenticated requests, allowing repeated requests to consume available memory. No credentials or user interaction are required; the documented consequence is memory exhaustion and denial of service, not data disclosure or modification.
The record
- CVE
- CVE-2021-26090
- Published
- Jul 12, 2021
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiMail
- Classifications
- CWE-401, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 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=FortiMail 6.4.0 through 6.4.4 and 6.2.0 through 6.2.6
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