KMail since version 5.3.0 used a QWebEngine based viewer that had JavaScript enabled.
KMail since version 5.3.0 used a QWebEngine based viewer that had JavaScript enabled.
No KDE vulnerabilities are listed in CISA KEV.
10 records in Kmail · all components
KMail since version 5.3.0 used a QWebEngine based viewer that had JavaScript enabled.
Through a malicious URL that contained a quote character it was possible to inject HTML code in KMail's plaintext viewer.
KDE kmail before 5.5.2 and messagelib before 5.5.2, as distributed in KDE Applications before 17.04.2, do not ensure that a plugin's sign/encrypt action occurs during use of the Send Later feature, which allows remote at…
The S/MIME specification allows a Cipher Block Chaining (CBC) malleability-gadget attack that can indirectly lead to plaintext exfiltration, aka EFAIL.
An issue was discovered in KDE KMail before 19.12.3.
KMail since version 5.3.0 used a QWebEngine based viewer that had JavaScript enabled.
KDE KMail 19.12.3 (aka 5.13.3) engages in unencrypted POP3 communication during times when the UI indicates that encryption is in use.
KDE KMail does not encrypt attachments in emails when "automatic encryption" is enabled, which allows remote attackers to obtain sensitive information by sniffing the network.
In KDE KMail 19.12.3 (aka 5.13.3), the SMTP STARTTLS option is not honored (and cleartext messages are sent) unless "Server requires authentication" is checked.
In KDE KMail 5.2.3, an attacker in possession of S/MIME or PGP encrypted emails can wrap them as sub-parts within a crafted multipart email.