CVE-2024-41959

7.6 HIGH

📋 TL;DR

This is a cross-site scripting (XSS) vulnerability in mailcow: dockerized that allows unauthenticated attackers to inject malicious JavaScript into API logs. When administrators view these logs, the script executes in their browser context, potentially enabling session hijacking, data theft, or unauthorized actions. All mailcow installations running versions before the July 2024 release are affected.

💻 Affected Systems

Products:
  • mailcow: dockerized
Versions: All versions before 2024-07 release
Operating Systems: Any OS running Docker
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all default installations; vulnerability exists in the API logging functionality.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could steal administrator session cookies, gain full control of the mailcow instance, access all email accounts, and pivot to internal network systems.

🟠

Likely Case

Attackers would steal administrator credentials or session tokens to gain unauthorized access to the mailcow administration panel.

🟢

If Mitigated

With proper network segmentation and access controls, impact would be limited to the mailcow instance itself.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires no authentication and involves simple JavaScript injection; weaponization is likely due to the popularity of mailcow.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2024-07 release

Vendor Advisory: https://github.com/mailcow/mailcow-dockerized/security/advisories/GHSA-v3r3-8f69-ph29

Restart Required: Yes

Instructions:

1. Backup your mailcow configuration and data. 2. Navigate to your mailcow directory. 3. Run: git fetch origin master. 4. Run: git checkout 2024-07. 5. Run: docker compose pull. 6. Run: docker compose up -d. 7. Verify services are running properly.

🔧 Temporary Workarounds

No workarounds available

all

The vendor states there are no known workarounds for this vulnerability.

🧯 If You Can't Patch

  • Restrict access to the mailcow administration interface to trusted IP addresses only using firewall rules.
  • Implement strong authentication mechanisms and monitor for unusual administrator login activity.

🔍 How to Verify

Check if Vulnerable:

Check your mailcow version by running: cd /path/to/mailcow && grep MAILCOW_VERSION mailcow.conf

Check Version:

cd /path/to/mailcow && grep MAILCOW_VERSION mailcow.conf

Verify Fix Applied:

Verify version shows 2024-07 or later and test that JavaScript injection into API logs no longer executes when viewing logs.

📡 Detection & Monitoring

Log Indicators:

  • Unusual API requests containing JavaScript payloads
  • Multiple failed login attempts followed by successful logins

Network Indicators:

  • HTTP requests to mailcow API endpoints with JavaScript in parameters

SIEM Query:

source="mailcow" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export