{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-24760 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-24760 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-24760 is a high-severity vulnerability in mailcow-dockerized, published on 2 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-24760 and fix it if it is affected.\n\nWhat it is: CVE-2024-24760 is a high-severity vulnerability in mailcow-dockerized, published on 2 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-24760 in the wild and no public exploit code.\n\nAffected product: mailcow-dockerized. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-24760/ (Markdown: https://insights.sbomify.com/CVE-2024-24760/index.md)","id":"CVE-2024-24760","markdown":"https://insights.sbomify.com/CVE-2024-24760/index.md","name":"CVE-2024-24760","record":{"aliases":["GHSA-gmpj-5xcm-xxx6"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Mailcow Docker package","requires_auth":"low_privilege","summary":"Attackers on the same subnet can access internal Docker container ports despite localhost binding, potentially exposing sensitive data or services.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mailcow\\","vendor":"mailcow"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-610","name":"Externally Controlled Reference to a Resource in Another Sphere"}],"description":"mailcow is a dockerized email package, with multiple containers linked in one bridged network. A security vulnerability has been identified in mailcow affecting versions \u003c 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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-03-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-03-04T00:53:35Z","kind":"github_poc","ref":"https://github.com/killerbees19/CVE-2024-24760","stars":0,"title":"mailcow: Docker Container Exposure to Local Network"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Mailcow Docker Container Exposure to Local Network","id":"CVE-2024-24760","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Galette public pages accessibility restriction","id":"CVE-2024-24761"},"packages":[],"prev":{"headline":"MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding","id":"CVE-2024-24759"},"products":["mailcow-dockerized"],"published":"2024-02-02","related":[{"cvss_score":9.1,"headline":"mailcow: dockerized vulnerable to SSTI in Quota and Quarantine Notification Template","id":"CVE-2025-53909","kev_date_added":null,"published":"2025-07-17"},{"cvss_score":8.8,"headline":"Manipulation of Internal Dovecot Variables in mailcow via crafted Passwords","id":"CVE-2023-34108","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":8.8,"headline":"OS Command Injection in mailcow","id":"CVE-2022-31138","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-31245","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-8928","kev_date_added":null,"published":"2017-05-14"},{"cvss_score":8.3,"headline":"mailcow-dockerized XSS Vulnerability in Quarantine UI Allows Unauthorized Access and Data Manipulation","id":"CVE-2023-49077","kev_date_added":null,"published":"2023-11-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-15","vendors":["mailcow"]},"summary":"Attackers on the same subnet can access internal Docker container ports despite localhost binding, potentially exposing sensitive data or services.","url":"https://insights.sbomify.com/CVE-2024-24760/"}