CVE-2024-24760: Mailcow Docker Container Exposure to Local Network
mailcow is a dockerized email package, with multiple containers linked in one bridged network. A security vulnerability has been identified in mailcow affecting versions < 2024-01c. This vulnerability potentially allows attackers on the same subnet to connect to exposed ports of a Docker container, even when the port is bound to 127.0.0.1. The vulnerability has been addressed by implementing additional iptables/nftables rules. These rules drop packets for Docker containers on ports 3306, 6379, 8983, and 12345, where the input interface is not br-mailcow and the output interface is br-mailcow.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Implement iptables/nftables rules to drop packets for mailcow Docker containers on ports 3306, 6379, 8983, and 12345 when the input interface is NOT `br-mailcow` and the output interface IS `br-mailcow`, per the described mitigation for Mailcow Docker Container Exposure to Local Network.
Event History
Frequently Asked Questions
What is the severity of CVE-2024-24760?
CVE-2024-24760 has a medium severity rating due to the potential for local attackers to exploit exposed ports.
How do I fix CVE-2024-24760?
To fix CVE-2024-24760, upgrade mailcow to version 2024-01c or later.
What versions of mailcow are affected by CVE-2024-24760?
CVE-2024-24760 affects all mailcow versions prior to 2024-01c.
Can CVE-2024-24760 be exploited remotely?
CVE-2024-24760 cannot be exploited remotely and requires an attacker to be on the same subnet.
What containers in mailcow are impacted by CVE-2024-24760?
CVE-2024-24760 impacts all mailcow containers that expose ports to the same bridged network.