# CVE-2024-3408: Authentication Bypass and RCE in man-group/dtale > Attackers can bypass authentication and execute arbitrary code on dtale servers due to hardcoded secrets and improper input validation. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 6 Jun 2024 - **Updated:** 3 Nov 2024 - **Also known as:** GHSA-v9q6-fm48-rx74, PYSEC-2024-117 ## What is CVE-2024-3408? CVE-2024-3408 is a critical authentication bypass vulnerability in man-group/dtale, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description man-group/dtale version 3.10.0 is vulnerable to an authentication bypass and remote code execution (RCE) due to improper input validation. The vulnerability arises from a hardcoded `SECRET_KEY` in the flask configuration, allowing attackers to forge a session cookie if authentication is enabled. Additionally, the application fails to properly restrict custom filter queries, enabling attackers to execute arbitrary code on the server by bypassing the restriction on the `/update-settings` endpoint, even when `enable_custom_filters` is not enabled. This vulnerability allows attackers to bypass authentication mechanisms and execute remote code on the server. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-798 (Use of Hard-coded Credentials) ## Which versions are affected by CVE-2024-3408? 3 open source packages ship an affected version, including dtale. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `dtale` | PyPI | All versions | None | | `dtale` | PyPI | All versions to 3.10.0 | None | | `dtale` | PyPI | All versions to 3.10.0 | None | Products: Man D-Tale. ## How do I fix CVE-2024-3408? No fix has been published for CVE-2024-3408 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-3408 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3408 exists. Public exploit code: - D-Tale RCE (metasploit) - Vuln lab for CVE-2024-3408 - D-Tale Authentication Bypass & RCE (github_poc): https://github.com/flame-11/CVE-2024-3408-dtale - D-Tale 3.10.0 - 3.15.1 - Authentication Bypass & Remote Code Execution (nuclei): http/cves/2024/CVE-2024-3408.yaml ## Other vulnerabilities in man-group/dtale - [CVE-2026-27194](https://insights.sbomify.com/CVE-2026-27194/): D-Tale affected by Remote Code Execution through the /save-column-filter endpoint (high 8.1) - [CVE-2024-21642](https://insights.sbomify.com/CVE-2024-21642/): D-Tale server-side request forgery through Web uploads (high 7.5) - [CVE-2024-45595](https://insights.sbomify.com/CVE-2024-45595/): D-Tale allows Remote Code Execution through the Query input on Chart Builder (medium 6.1) - [CVE-2023-46134](https://insights.sbomify.com/CVE-2023-46134/): D-Tale vulnerable to Remote Code Execution through the Custom Filter Input (medium 6.1) - [CVE-2026-35052](https://insights.sbomify.com/CVE-2026-35052/): D-Tale affected by Remote Code Execution through redis/shelf storage (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3408 and fix it if it is affected. What it is: CVE-2024-3408 is a critical authentication bypass vulnerability in man-group/dtale, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3408 exists. Affected packages and fixed versions: - dtale (PyPI): affected all versions; no fix listed - dtale (PyPI): affected all versions up to 3.10.0; no fix listed - dtale (PyPI): affected all versions up to 3.10.0; no fix listed 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-3408/ (Markdown: https://insights.sbomify.com/CVE-2024-3408/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3408 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3408 - OSV: https://osv.dev/vulnerability/CVE-2024-3408 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3408/ Summaries are generated and may contain mistakes; the official description above is the record.