SQ40103
Detected container images that might expose the FTP port.
| priority | CI/CD status | severity | effort | SAFE level | SAFE assessment |
|---|---|---|---|---|---|
 | pass | high | medium | None | hardening: warning Reason: exposed container ports |
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 it might seem practical for data sharing, FTP is an insecure protocol that transmits unencrypted credentials, and can inadvertently expose sensitive files if not configured properly. Additionally, containers should only mount volumes with data required by containerized services during their execution, and are typically not used for long-term storage.
How to resolve the issue
- You should not run FTP in containers.
- Check if there's a running FTP daemon or service in the container's process list bound to port 21, or if one is executed on startup, and remove it.
Incidence statistics
ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes. Analysis results are used to calculate incidence statistics for issues (policy violations) that Spectra Assure can detect in software packages.
This section is updated when new data becomes available.
Total amount of packages analyzed
- RubyGems: 183K
- Nuget: 644K
- PyPi: 628K
- NPM: 3.72M
Recommended reading
- Docker Expose Port: What It Means and What It Doesn't Mean (External resource - CloudBees)
- FTP Server (External resource - Ubuntu)