SQ40104
Detected container images that might expose the SSH port.
| priority | CI/CD status | severity | effort | RL level | RL assessment |
|---|---|---|---|---|---|
 | pass | high | medium | None | None |
About the issue
Containers are a simple, yet powerful approach to process and filesystem isolation. When configured correctly, a container runs a set of processes isolated from their host system. Containers typically run as executables or as services, but regardless of their use, they must be properly secured. Although remote access services (such as SSH) might seem practical for administration, their use can lead to bad practices like hard-coded credentials and keys, and can additionally increase the attack surface by providing an obvious entry point in an environment.
How to resolve the issue
- Avoid running remote access services such as SSH.
- Check if there's a running SSH daemon or service in the container's process list bound to port 22, or if one is executed on startup, and remove it.
Recommended reading
- Docker Expose Port: What It Means and What It Doesn't Mean (External resource - CloudBees)
- What is SSH (Secure Shell)? (External resource - SSH)
- Remote access service (External resource - Wikipedia)