{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41083 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41083 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41083 is a high-severity vulnerability in justingit dada-mail, published on 20 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-41083 and fix it if it is affected.\n\nWhat it is: CVE-2021-41083 is a high-severity vulnerability in justingit dada-mail, published on 20 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-41083 in the wild and no public exploit code.\n\nAffected product: justingit dada-mail. 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-2021-41083/ (Markdown: https://insights.sbomify.com/CVE-2021-41083/index.md)","id":"CVE-2021-41083","markdown":"https://insights.sbomify.com/CVE-2021-41083/index.md","name":"CVE-2021-41083","record":{"aliases":["GHSA-344m-p829-2r38"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Email list management","requires_auth":"low_privilege","summary":"Attackers can hijack admin sessions via CSRF to take full control of mailing lists and change passwords, requiring users to upgrade.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dada_mail","vendor":"dadamailproject"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Dada Mail is a web-based e-mail list management system. In affected versions a bad actor could give someone a carefully crafted web page via email, SMS, etc, that - when visited, allows them control of the list control panel as if the bad actor was logged in themselves. This includes changing any mailing list password, as well as the Dada Mail Root Password - which could effectively shut out actual list owners of the mailing list and allow the bad actor complete and unfettered control of your mailing list. This vulnerability also affects profile logins. For this vulnerability to work, the target of the bad actor would need to be logged into the list control panel themselves. This CSRF vulnerability in Dada Mail affects all versions of Dada Mail v11.15.1 and below. Although we know of no known CSRF exploits that have happened in the wild, this vulnerability has been confirmed by our testing, and by a third party. Users are advised to update to version 11.16.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CSRF Vulnerability in dada-mail 11.15.1 and below","id":"CVE-2021-41083","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Response Splitting from unsanitized headers in http4s","id":"CVE-2021-41084"},"packages":[],"prev":{"headline":"Private message title and participating users leaked in discourse","id":"CVE-2021-41082"},"products":["dada-mail"],"published":"2021-09-20","related":[],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["justingit"]},"summary":"Attackers can hijack admin sessions via CSRF to take full control of mailing lists and change passwords, requiring users to upgrade.","url":"https://insights.sbomify.com/CVE-2021-41083/"}