{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3748 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3748 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3748 is a high-severity vulnerability in Google Android, published on 29 Jun 2017. 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-2017-3748 and fix it if it is affected.\n\nWhat it is: CVE-2017-3748 is a high-severity vulnerability in Google Android, published on 29 Jun 2017. 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-2017-3748 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-3748/ (Markdown: https://insights.sbomify.com/CVE-2017-3748/index.md)","id":"CVE-2017-3748","markdown":"https://insights.sbomify.com/CVE-2017-3748/index.md","name":"CVE-2017-3748","record":{"aliases":["GHSA-g7gx-c2jg-7cg5"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lenovo Vibe mobile phone","requires_auth":"low_privilege","summary":"Attackers can exploit improper access controls in the nac_server component to elevate privileges to root on Lenovo Vibe devices.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[{"product":"android","vendor":"google"}],"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":[],"description":"On Lenovo VIBE mobile phones, improper access controls on the nac_server component can be abused in conjunction with CVE-2017-3749 and CVE-2017-3750 to elevate privileges to the root user (commonly known as 'rooting' or \"jail breaking\" a device).","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":"Privilege escalation in Lenovo Vibe and Lenovo China-only Moto Mobile Phones","id":"CVE-2017-3748","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Lenovo Vibe and Lenovo China-only Moto Mobile Phones","id":"CVE-2017-3749"},"packages":[],"prev":{"headline":"Privilege escalation in Lenovo Nerve Center","id":"CVE-2017-3747"},"products":["Lenovo Vibe and Lenovo China-only Moto Mobile Phones"],"published":"2017-06-29","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-09-16","vendors":["Lenovo Group Ltd."]},"summary":"Attackers can exploit improper access controls in the nac_server component to elevate privileges to root on Lenovo Vibe devices.","url":"https://insights.sbomify.com/CVE-2017-3748/"}