Is port 28017 (MongoDB HTTP Status) dangerous?

Port 28017 is classified as critical risk and should not be exposed to the public internet. It transmits data without encryption, making it vulnerable to eavesdropping and credential theft.

Should port 28017 be open on my firewall?

No, port 28017 should not be open to the public internet. Block it at the firewall and use encrypted alternatives such as SSH, SFTP, or HTTPS instead.

What transport protocol does port 28017 use?

Port 28017 (MongoDB HTTP Status) uses the TCP transport protocol and falls under the Database category.

:28017 (TCP)

MongoDB HTTP Status

Critical Riesgo

TCP — Database

Resumen del puerto

Número de puerto 28017

Nombre del servicio MongoDB HTTP Status

Protocolo de transporte TCP

Categoría Database

Riesgo de seguridad Critical

Rango de puertos Registrados (1024-49151)

Qué es el puerto 28017?

Previously used by MongoDB for its built-in HTTP status interface and REST API, deprecated in MongoDB 3.2 and removed in 3.6. Historically exposed database statistics and admin information over HTTP without authentication. Should be blocked on any legacy MongoDB deployments.

TCP Database

Consideraciones de seguridad

El puerto 28017 (MongoDB HTTP Status) está clasificado como riesgo crítico. Este puerto no debe exponerse a internet público. El servicio transmite datos sin cifrado, haciéndolo vulnerable a escuchas, robo de credenciales y ataques de intermediario.

Recomendación: Bloquea este puerto en el firewall. Utiliza alternativas cifradas (SSH, SFTP, HTTPS) en su lugar.

Puertos relacionados — Database

66 Oracle SQL*NET 118 SQL Services 134 INGRES-NET 142 BL-IDM 150 SQL-NET 156 SQL Service 181 Unify 188 MUMPS

Términos relacionados

ASN BGP Hijack Data Center Domain Name Dual Stack Internet Exchange Point (IXP)