Email plaintext recovery via missing cryptographic step
Published Jul 9, 2021 · Updated Oct 25, 2024
Cryptographic verification failure in Fortinet FortiMail before 7.0.0 allows man-in-the-middle attackers to recover email plaintext. The IBE service omits an unspecified cryptographic step, allowing intercepted ciphertext to be altered without tampering detection. Exploitation requires interception of encrypted messages and exposes their contents; no service interruption or configuration change is reported.
Summary
What happened
Cryptographic verification failure in Fortinet FortiMail before 7.0.0 allows man-in-the-middle attackers to recover email plaintext. The IBE service omits an unspecified cryptographic step, allowing intercepted ciphertext to be altered without tampering detection. Exploitation requires interception of encrypted messages and exposes their contents; no service interruption or configuration change is reported.
The record
- CVE
- CVE-2021-26100
- Published
- Jul 9, 2021
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiMail
- Classifications
- CWE-347, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 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 before 7.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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