2021-38373 | KDE KMail SMTP STARTTLS cleartext transmission
|CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability, which was classified as problematic, was found in KDE KMail 19.12.3 (Mail Client Software). This affects an unknown code block of the component SMTP STARTTLS Handler. The manipulation with an unknown input leads to a weak encryption vulnerability. CWE is classifying the issue as CWE-319. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The weakness was disclosed 08/10/2021. It is possible to read the advisory at bugs.kde.org. This vulnerability is uniquely identified as CVE-2021-38373 since 08/10/2021. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.7
Status: Not defined
0-Day Time: 🔒
Download the whitepaper to learn more about our service!