Credential and message disclosure via ignored TLS errors
Published Jun 25, 2020 · Updated Aug 4, 2024
Improper certificate validation in Trojita before 0.8 allows man-in-the-middle attackers to read SMTP credentials and sent messages. MSA/SMTP.cpp silently ignores certificate-verification errors and continues the SMTP TLS connection when the server presents an invalid certificate. Attackers must intercept outbound mail traffic and impersonate the SMTP server; Trojita then transmits the username, password, and message content.
Summary
What happened
Improper certificate validation in Trojita before 0.8 allows man-in-the-middle attackers to read SMTP credentials and sent messages. MSA/SMTP.cpp silently ignores certificate-verification errors and continues the SMTP TLS connection when the server presents an invalid certificate. Attackers must intercept outbound mail traffic and impersonate the SMTP server; Trojita then transmits the username, password, and message content.
The record
- CVE
- CVE-2020-15047
- Published
- Jun 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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