# CVE-2024-41958: Two-Factor Authentication (2FA) Bypass in mailcow: dockerized

> An authenticated attacker with target credentials can bypass two-factor authentication to gain unauthorized access to other accounts in mailcow.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2024
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4fcc-q245-qqgg

## What is CVE-2024-41958?

CVE-2024-41958 is a medium-severity authentication bypass vulnerability in mailcow-dockerized, published on 5 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

mailcow: dockerized is an open source groupware/email suite based on docker. A vulnerability has been discovered in the two-factor authentication (2FA) mechanism. This flaw allows an authenticated attacker to bypass the 2FA protection, enabling unauthorized access to other accounts that are otherwise secured with 2FA. To exploit this vulnerability, the attacker must first have access to an account within the system and possess the credentials of the target account that has 2FA enabled. By leveraging these credentials, the attacker can circumvent the 2FA process and gain access to the protected account. This issue has been addressed in the `2024-07` release. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-697 (Incorrect Comparison)

## Which versions are affected by CVE-2024-41958?

It affects 1 product.


Products: Mailcow Mailcow\.

## How do I fix CVE-2024-41958?

No fix has been published for CVE-2024-41958 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41958 being exploited?

There is no known exploitation of CVE-2024-41958 in the wild and no public exploit code.

Public exploit code:

- This is a small proof of concept for CVE-2024-41958 (github_poc): https://github.com/OrangeJuiceHU/CVE-2024-41958-PoC

## Other vulnerabilities in mailcow-dockerized

- [CVE-2025-53909](https://insights.sbomify.com/CVE-2025-53909/): mailcow: dockerized vulnerable to SSTI in Quota and Quarantine Notification Template (critical 9.1)
- [CVE-2024-24760](https://insights.sbomify.com/CVE-2024-24760/): Mailcow Docker Container Exposure to Local Network (high 8.8)
- [CVE-2023-34108](https://insights.sbomify.com/CVE-2023-34108/): Manipulation of Internal Dovecot Variables in mailcow via crafted Passwords (high 8.8)
- [CVE-2022-31138](https://insights.sbomify.com/CVE-2022-31138/): OS Command Injection in mailcow (high 8.8)
- [CVE-2022-31245](https://insights.sbomify.com/CVE-2022-31245/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41958 and fix it if it is affected.

What it is: CVE-2024-41958 is a medium-severity authentication bypass vulnerability in mailcow-dockerized, published on 5 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41958 in the wild and no public exploit code.

Affected product: mailcow-dockerized. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41958/ (Markdown: https://insights.sbomify.com/CVE-2024-41958/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41958
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41958
- OSV: https://osv.dev/vulnerability/CVE-2024-41958

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41958/
Summaries are generated and may contain mistakes; the official description above is the record.