{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18653 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18653 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18653 is a medium-severity missing authorization vulnerability in Google Android, published on 7 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18653 and fix it if it is affected.\n\nWhat it is: CVE-2017-18653 is a medium-severity missing authorization vulnerability in Google Android, published on 7 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-18653 in the wild and no public exploit code.\n\nAffected product: Google Android. 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-2017-18653/ (Markdown: https://insights.sbomify.com/CVE-2017-18653/index.md)","id":"CVE-2017-18653","markdown":"https://insights.sbomify.com/CVE-2017-18653/index.md","name":"CVE-2017-18653","record":{"aliases":["GHSA-h83r-q55f-q6p9"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_modify","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Email app","requires_auth":"low_privilege","summary":"Attackers can send emails on behalf of any user via a broadcasted intent in the Samsung Email application, requiring a security patch.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software. The Email application allows attackers to send emails on behalf of any user via a broadcasted intent. The Samsung ID is SVE-2017-9357 (September 2017).","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":"Missing authorization in n/a","id":"CVE-2017-18653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2017-18654"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2017-18652"},"products":["n/a"],"published":"2020-04-07","related":[{"cvss_score":8.8,"headline":"Google Pixel Improper Authorization","id":"CVE-2026-58704","kev_date_added":"2026-09-16","published":"2026-09-15"},{"cvss_score":8.8,"headline":"Android Runtime Use-After-Free","id":"CVE-2025-48543","kev_date_added":"2025-09-04","published":"2025-09-04"},{"cvss_score":8.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2023-35674","kev_date_added":"2023-09-13","published":"2023-09-11"},{"cvss_score":8.4,"headline":"Android Framework Integer Overflow","id":"CVE-2025-48595","kev_date_added":"2026-06-02","published":"2026-06-01"},{"cvss_score":8.1,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-32896","kev_date_added":"2024-06-13","published":"2024-06-13"},{"cvss_score":7.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2025-48572","kev_date_added":"2025-12-02","published":"2025-12-08"},{"cvss_score":7.8,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-29748","kev_date_added":"2024-04-04","published":"2024-04-05"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can send emails on behalf of any user via a broadcasted intent in the Samsung Email application, requiring a security patch.","url":"https://insights.sbomify.com/CVE-2017-18653/"}