Claws Mail
Products by Claws Mail Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 0 vulnerabilities in Claws Mail . Claws Mail did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 1 | 6.10 |
| 2020 | 2 | 8.65 |
| 2019 | 1 | 4.30 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Claws Mail vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Claws Mail Security Vulnerabilities
textview_uri_security_check in textview.c in Claws Mail before 3.18.0
CVE-2021-37746
6.1 - Medium
- July 30, 2021
textview_uri_security_check in textview.c in Claws Mail before 3.18.0, and Sylpheed through 3.7.0, does not have sufficient link checks before accepting a click.
Open Redirect
In imap_scan_tree_recursive in Claws Mail through 3.17.6, a malicious IMAP server can trigger stack consumption
CVE-2020-16094
7.5 - High
- July 28, 2020
In imap_scan_tree_recursive in Claws Mail through 3.17.6, a malicious IMAP server can trigger stack consumption because of unlimited recursion into subdirectories during a rebuild of the folder tree.
Stack Exhaustion
common/session.c in Claws Mail before 3.17.6 has a protocol violation
CVE-2020-15917
9.8 - Critical
- July 23, 2020
common/session.c in Claws Mail before 3.17.6 has a protocol violation because suffix data after STARTTLS is mishandled.
In Claws Mail 3.14.1, an attacker in possession of S/MIME or PGP encrypted emails
CVE-2019-10735
4.3 - Medium
- April 07, 2019
In Claws Mail 3.14.1, an attacker in possession of S/MIME or PGP encrypted emails can wrap them as sub-parts within a crafted multipart email. The encrypted part(s) can further be hidden using HTML/CSS or ASCII newline characters. This modified multipart email can be re-sent by the attacker to the intended receiver. If the receiver replies to this (benign looking) email, they unknowingly leak the plaintext of the encrypted message part(s) back to the attacker.