Description (CNA)
Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports (secure: true) resolve the same non-IP host with different tls.servername values, the first transport's servername is returned on the cache hit and overwrites the second transport's explicitly configured value, so Nodemailer sends the wrong SNI value and validates the peer certificate against the wrong identity. In multi-tenant services or SNI-routed SMTP gateways, an attacker who can prime the cache can cause a victim transport to connect to the attacker's TLS virtual host and accept the attacker's certificate even with rejectUnauthorized: true, disclosing the victim's SMTP credentials. Fixed in 10.0.2.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| nodemailer / nodemailer | affected 5.0.0 before 10.0.2; unaffected 10.0.2 |
CWE
CWE-295
References
- https://github.com/nodemailer/nodemailer/security/advisories/GHSA-6vj9-mwq6-2f5v
- https://www.vulncheck.com/advisories/nodemailer-5.0.0-through-10.0.1-tls-servername-cache-confusion
ADP enrichment
No English description supplied.
No references supplied.