TCP
Почта
Порт 587 (SMTP Submission)
Узнайте о порте 587 (SMTP Submission) - угрозы безопасности, уязвимости и применение. Найдите устройства с открытым портом 587.
Краткая информация
Номер порта
587
Протокол
TCP
Сервис
SMTP Submission
Имя IANA
SMTP Submission
Описание сервиса
Port 587 (TCP) is the standard port for SMTP Submission, as defined in RFC 8314. It is used by Message Submission Agents (MSAs) to accept email from mail clients for relaying to an email server. Unlike port 25 (SMTP), which is primarily used for server-to-server email transfer, port 587 is specifically designed for client-to-server communication. This differentiation allows for stricter authentication and encryption policies to be enforced, mitigating spam and other email-based threats. Historically, port 25 was often used for both client submission and server relay, but the rise of spam necessitated a separation of roles, leading to the adoption of port 587. The protocol used on port 587 is SMTP, but it mandates the use of Message Submission, typically requiring authentication via protocols such as STARTTLS followed by SASL (Simple Authentication and Security Layer) mechanisms like PLAIN, LOGIN, or CRAM-MD5. This ensures that only authorized users can submit mail through the server.
At a technical level, when a mail client wants to send an email, it connects to the MSA on port 587. The MSA then initiates a TLS handshake using STARTTLS to establish an encrypted connection. Following successful encryption, the client authenticates using SASL, providing credentials to prove its identity. Once authenticated, the client can then send the email message to the MSA using the standard SMTP protocol verbs (MAIL FROM, RCPT TO, DATA). The MSA then relays the message to the appropriate destination mail server, either directly or through other mail relay servers. This process ensures that outgoing email is properly authenticated and encrypted, preventing unauthorized access and tampering.
## Firewall Recommendations
Port 587 should be allowed for outbound connections from internal mail clients to the organization's mail server(s). For inbound connections, port 587 should only be allowed from authorized networks or clients that require direct submission to the mail server (e.g., remote users). It is crucial to block port 587 for inbound connections from untrusted networks to prevent unauthorized email submission. Best practices include implementing strong authentication mechanisms (e.g., SASL with strong passwords or certificate-based authentication), enforcing TLS encryption with strong ciphers, and regularly updating the mail server software to patch security vulnerabilities. Rate limiting can also be implemented to prevent abuse and denial-of-service attacks. Consider using a dedicated mail gateway to filter and scan outgoing email for spam and malware.
At a technical level, when a mail client wants to send an email, it connects to the MSA on port 587. The MSA then initiates a TLS handshake using STARTTLS to establish an encrypted connection. Following successful encryption, the client authenticates using SASL, providing credentials to prove its identity. Once authenticated, the client can then send the email message to the MSA using the standard SMTP protocol verbs (MAIL FROM, RCPT TO, DATA). The MSA then relays the message to the appropriate destination mail server, either directly or through other mail relay servers. This process ensures that outgoing email is properly authenticated and encrypted, preventing unauthorized access and tampering.
## Firewall Recommendations
Port 587 should be allowed for outbound connections from internal mail clients to the organization's mail server(s). For inbound connections, port 587 should only be allowed from authorized networks or clients that require direct submission to the mail server (e.g., remote users). It is crucial to block port 587 for inbound connections from untrusted networks to prevent unauthorized email submission. Best practices include implementing strong authentication mechanisms (e.g., SASL with strong passwords or certificate-based authentication), enforcing TLS encryption with strong ciphers, and regularly updating the mail server software to patch security vulnerabilities. Rate limiting can also be implemented to prevent abuse and denial-of-service attacks. Consider using a dedicated mail gateway to filter and scan outgoing email for spam and malware.
Информация о безопасности
While port 587 is designed with security in mind, it is still susceptible to certain attacks if not properly configured and maintained. A common vulnerability is the failure to enforce strong authentication mechanisms or to properly implement TLS. Weak or outdated TLS configurations can be exploited by attackers to eavesdrop on email traffic or perform man-in-the-middle attacks. If authentication is not required or if weak authentication methods are used (e.g., allowing anonymous relay), spammers can abuse the server to send unsolicited emails. Additionally, vulnerabilities in the underlying SMTP server software can be exploited to gain unauthorized access or execute arbitrary code. Attackers often target port 587 because it is a common entry point for sending email, and a compromised server can be used to distribute spam, phishing emails, or malware.
Известные уязвимости
| CVE | Название | Критичность | Описание |
|---|---|---|---|
| CVE-2023-51765 | Postfix before 3.8.4 and 3.9 before 3.9-20231217 allows STARTTLS command injection | Medium | Postfix before 3.8.4 and 3.9 before 3.9-20231217 allows STARTTLS command injection. When Postfix receives the STARTTLS command from a client, it continues to parse commands from the client during the TLS handshake. This allows an attacker to inject arbitrary commands into the Postfix SMTP session after the TLS handshake is complete. This can be exploited to bypass security checks or execute arbitrary commands. |
| CVE-2023-4287 | Exim SMTP service Stack-based buffer overflow | Critical | A stack-based buffer overflow vulnerability exists in the SMTP service of Exim. This vulnerability is due to a failure to properly validate the length of user-supplied data, which can result in a write past the end of the allocated buffer. An attacker can leverage this vulnerability to execute arbitrary code in the context of the service account. |
Распространённое ПО
- Postfix
- Sendmail
- Exim
- Microsoft Exchange Server
- hMailServer
- Zimbra Collaboration Suite
- Courier Mail Server
- Dovecot (MSA implementation)
Найти устройства с этим портом
Обнаружьте все устройства с открытым портом 587 в любой стране.
Искать порт 587Найдите все устройства с открытым портом 587
ScaniteX сканирует миллионы IP-адресов для поиска устройств с определёнными открытыми портами. Идеально для исследований безопасности и аудита сети.
Начать массовое сканирование
RU
English