Skip to main content

Security Exposure

A submission server accepts logins, so an exposed 465 listener draws credential guessing and reuse of stolen passwords. Microsoft notes that Basic authentication makes credential capture easier and that enforcing MFA is not simple, or in some cases not possible, while Basic authentication stays enabled. Stolen credentials can also be reused against other services.

Hardening

  • Require SMTP authentication for every submission; RFC 6409 has message submission agents reject unauthenticated MAIL commands by default.
  • Support TLS 1.2 or later, as RFC 8314 requires of submission servers, and disable TLS 1.0 and 1.1, which RFC 8996 deprecates.
  • Prefer modern authentication (OAuth) over Basic authentication where the mail platform supports it.
  • Rate-limit and lock out repeated failed logins per account and per source address.

Monitoring

Log authentication successes and failures on the submission service and alert on spikes from single sources or across many accounts. Watch outbound mail volume per account for signs of a compromised mailbox.

SMTPS (submissions) Vulnerabilities

6 CVEs
CVECVSS
CVE-2010-4344KEV
Exim Heap-Based Buffer Overflow Vulnerability
9.8
CVE-2010-4345KEV
Exim Privilege Escalation Vulnerability
7.8
CVE-2019-16928KEV
Exim Out-of-bounds Write Vulnerability
9.8
CVE-2019-10149KEV
Exim Mail Transfer Agent (MTA) Improper Input Validation
9.0
CVE-2018-6789KEV
Exim Buffer Overflow Vulnerability
9.8
CVE-2026-4020
Gravity SMTP <= 2.1.4 - Unauthenticated Sensitive Information Exposure via REST API
7.5

Frequently Asked Questions

Port 465 or 587: which should be used?→

RFC 8314 says clients and servers should implement both: implicit TLS on 465 and STARTTLS on 587. It also notes no significant difference in security between the two when both are implemented correctly.

Is port 465 deprecated?→

No. RFC 8314 registered port 465 for the submissions service, documenting its existing wide use for implicit TLS submission.

Which vulnerabilities affect the service on port 465?→

This database lists 6 CVEs related to SMTPS (submissions), 5 of them confirmed as exploited by CISA. Examples: CVE-2010-4344, CVE-2010-4345, CVE-2019-16928, CVE-2019-10149.

Port assignments from the IANA Service Name and Transport Protocol Port Number Registry. Services can be configured to run on any port, so traffic on port 465 is not guaranteed to be SMTPS (submissions). Exploited-in-the-wild data from the CISA KEV catalog (CC0).