{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10497 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10497 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10497 is a high-severity code injection vulnerability in Samsung Email, published on 24 Sep 2018. 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-2018-10497 and fix it if it is affected.\n\nWhat it is: CVE-2018-10497 is a high-severity code injection vulnerability in Samsung Email, published on 24 Sep 2018. 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-2018-10497 in the wild and no public exploit code.\n\nAffected product: Samsung Email. 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-2018-10497/ (Markdown: https://insights.sbomify.com/CVE-2018-10497/index.md)","id":"CVE-2018-10497","markdown":"https://insights.sbomify.com/CVE-2018-10497/index.md","name":"CVE-2018-10497","record":{"aliases":["GHSA-24qg-gp8x-cc5w"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Email app","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by exploiting improper validation in EML file handling to execute arbitrary JavaScript.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"samsung_email","vendor":"samsung"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"This vulnerability allows local attackers to escalate privileges on vulnerable installations of Samsung Email Fixed in version 5.0.02.16. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of EML files. The issue results from the lack of proper validation of user-supplied data, which can allow arbitrary JavaScript to execute. An attacker can leverage this vulnerability to escalate privileges to resources normally protected from the application. Was ZDI-CAN-5328.","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":"Code injection in Samsung Email","id":"CVE-2018-10497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in Samsung Email","id":"CVE-2018-10498"},"packages":[],"prev":{"headline":"Use after free in Samsung Internet Browser","id":"CVE-2018-10496"},"products":["Samsung Email"],"published":"2018-09-24","related":[{"cvss_score":6.2,"headline":"Information disclosure in Samsung email","id":"CVE-2022-36837","kev_date_added":null,"published":"2022-08-05"},{"cvss_score":5.5,"headline":"Path traversal in Samsung Email","id":"CVE-2018-10498","kev_date_added":null,"published":"2018-09-24"},{"cvss_score":4,"headline":"Missing authorization in Samsung Email","id":"CVE-2022-36864","kev_date_added":null,"published":"2022-09-09"},{"cvss_score":3.9,"headline":"Path traversal in Samsung Email","id":"CVE-2022-22287","kev_date_added":null,"published":"2022-01-07"}],"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-05","vendors":["Samsung"]},"summary":"Local attackers can escalate privileges by exploiting improper validation in EML file handling to execute arbitrary JavaScript.","url":"https://insights.sbomify.com/CVE-2018-10497/"}