{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14998 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14998 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14998 is a medium-severity vulnerability in n/a, published on 28 Dec 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-14998 and fix it if it is affected.\n\nWhat it is: CVE-2018-14998 is a medium-severity vulnerability in n/a, published on 28 Dec 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-14998 in the wild and no public exploit code.\n\nAffected product: n/a. 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-14998/ (Markdown: https://insights.sbomify.com/CVE-2018-14998/index.md)","id":"CVE-2018-14998","markdown":"https://insights.sbomify.com/CVE-2018-14998/index.md","name":"CVE-2018-14998","record":{"aliases":["GHSA-c93g-m344-2c3f"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android mobile device","requires_auth":"none","summary":"Attackers with physical access can escalate privileges to root on Leagoo P1 devices by modifying system properties to enable a root ADB shell.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"p1_firmware","vendor":"leagoo"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"The Leagoo P1 Android device with a build fingerprint of sp7731c_1h10_32v4_bird:6.0/MRA58K/android.20170629.214736:user/release-keys contains a hidden root privilege escalation capability to achieve command execution as the root user. They have made modifications that allow a user with physical access to the device to obtain a root shell via ADB by modifying read-only system properties at runtime. Specifically, modifying the ro.debuggable and the ro.secure system properties to a certain value and then restarting the ADB daemon allows for a root shell to be obtained via ADB.","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 n/a","id":"CVE-2018-14998","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-14999"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2018-14997"},"products":["n/a"],"published":"2018-12-28","related":[{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2018-14999","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":5.5,"headline":"Missing authorization in n/a","id":"CVE-2018-14997","kev_date_added":null,"published":"2019-04-25"}],"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":["n/a"]},"summary":"Attackers with physical access can escalate privileges to root on Leagoo P1 devices by modifying system properties to enable a root ADB shell.","url":"https://insights.sbomify.com/CVE-2018-14998/"}