{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3292 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-3292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-3292 is a medium-severity vulnerability in mailscanner, published on 12 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-3292 and fix it if it is affected.\n\nWhat it is: CVE-2010-3292 is a medium-severity vulnerability in mailscanner, published on 12 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2010-3292 in the wild and no public exploit code.\n\nAffected product: mailscanner. 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-2010-3292/ (Markdown: https://insights.sbomify.com/CVE-2010-3292/index.md)","id":"CVE-2010-3292","markdown":"https://insights.sbomify.com/CVE-2010-3292/index.md","name":"CVE-2010-3292","record":{"aliases":["GHSA-j6hx-4cv9-wrj8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MailScanner email filter","requires_auth":"low_privilege","summary":"Attackers can modify MailScanner configuration files via DNS spoofing because update scripts lack encryption or signature verification.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"mailscanner","vendor":"mailscanner"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"The update{_bad,}_phishing_sites scripts in mailscanner 4.79.11-2 downloads files and trusts them without using encryption (e.g., https) or digital signature checking which could allow an attacker to replace certain configuration files (e.g., phishing whitelist) via dns/packet spoofing.","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":"Supply chain in mailscanner","id":"CVE-2010-3292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2010"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2010-3293"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2010-3291"},"products":["mailscanner"],"published":"2019-11-12","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3470","kev_date_added":null,"published":"2005-11-02"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2005-1706","kev_date_added":null,"published":"2005-05-24"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2008-5312","kev_date_added":null,"published":"2008-12-03"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2008-5313","kev_date_added":null,"published":"2008-12-03"},{"cvss_score":6.4,"headline":"Security feature bypass in n/a","id":"CVE-2002-2228","kev_date_added":null,"published":"2007-10-14"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2010-3293","kev_date_added":null,"published":"2019-10-28"}],"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-07","vendors":["mailscanner"]},"summary":"Attackers can modify MailScanner configuration files via DNS spoofing because update scripts lack encryption or signature verification.","url":"https://insights.sbomify.com/CVE-2010-3292/"}