{"answers":{"affected":"It affects 8 products.","exploited":"There is no known exploitation of CVE-2019-9882 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9882 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9882 is a high-severity vulnerability in OAKlouds MailSherlock MSR35, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-9882 and fix it if it is affected.\n\nWhat it is: CVE-2019-9882 is a high-severity vulnerability in OAKlouds MailSherlock MSR35, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-9882 in the wild and no public exploit code.\n\nAffected product: OAKlouds MailSherlock MSR35. 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-2019-9882/ (Markdown: https://insights.sbomify.com/CVE-2019-9882/index.md)","id":"CVE-2019-9882","markdown":"https://insights.sbomify.com/CVE-2019-9882/index.md","name":"CVE-2019-9882","record":{"aliases":["GHSA-79pw-7m53-3xmf"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MailSherlock email appliance","requires_auth":"none","summary":"Attackers can exploit CSRF to add malicious email sources to the whitelist in MailSherlock MSR35 and MSR45 devices.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"twcert","cpe":[{"product":"msr35_isherlock-base","vendor":"hgiga"},{"product":"msr35_isherlock-sysinfo","vendor":"hgiga"},{"product":"msr35_isherlock-user","vendor":"hgiga"},{"product":"msr35_isherlock-useradmin","vendor":"hgiga"},{"product":"msr45_isherlock-base","vendor":"hgiga"},{"product":"msr45_isherlock-sysinfo","vendor":"hgiga"},{"product":"msr45_isherlock-user","vendor":"hgiga"},{"product":"msr45_isherlock-useradmin","vendor":"hgiga"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Multi modules of MailSherlock MSR35 and MSR45 lead to a CSRF vulnerability. It allows attacker to add malicious email sources into whitelist via user/save_list.php?ACSION=\u0026type=email\u0026category=white\u0026locate=big5\u0026cmd=add\u0026new=hacker@socialengineering.com\u0026new_memo=\u0026add=%E6%96%B0%E5%A2%9E without any authorizes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in MailSherlock MSR35","id":"CVE-2019-9882","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in MailSherlock MSR35","id":"CVE-2019-9883"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-9881"},"products":["MailSherlock MSR35","MailSherlock MSR45"],"published":"2019-06-03","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in MailSherlock MSR35","id":"CVE-2019-9883","kev_date_added":null,"published":"2019-06-03"}],"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":["OAKlouds"]},"summary":"Attackers can exploit CSRF to add malicious email sources to the whitelist in MailSherlock MSR35 and MSR45 devices.","url":"https://insights.sbomify.com/CVE-2019-9882/"}