{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14999 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14999 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14999 is a critical missing authorization vulnerability in n/a, published on 25 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-14999 and fix it if it is affected.\n\nWhat it is: CVE-2018-14999 is a critical missing authorization vulnerability in n/a, published on 25 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-14999 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-14999/ (Markdown: https://insights.sbomify.com/CVE-2018-14999/index.md)","id":"CVE-2018-14999","markdown":"https://insights.sbomify.com/CVE-2018-14999/index.md","name":"CVE-2018-14999","record":{"aliases":["GHSA-hfr6-3rjr-jmhf"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Android factory reset app","requires_auth":"none","summary":"A pre-installed Android app allows any local application to trigger a factory reset without permissions, causing total data loss.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"p1_firmware","vendor":"leagoo"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.0"},"cwes":[],"description":"The Leagoo P1 device with a build fingerprint of sp7731c_1h10_32v4_bird:6.0/MRA58K/android.20170629.214736:user/release-keys contains a pre-installed platform app with a package name of com.wtk.factory (versionCode=1, versionName=1.0) that contains an exported broadcast receiver named com.wtk.factory.MMITestReceiver allows any app co-located on the device to programmatically initiate a factory reset. In addition, the app initiating the factory reset does not require any permissions. A factory reset will remove all user data and apps from the device. This will result in the loss of any data that have not been backed up or synced externally. The capability to perform a factory reset is not directly available to third-party apps (those that the user installs themselves with the exception of enabled Mobile Device Management (MDM) apps), although this capability can be obtained by leveraging an unprotected app component of a pre-installed platform app.","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-2018-14999","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-15000"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2018-14998"},"products":["n/a"],"published":"2019-04-25","related":[{"cvss_score":6.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-14998","kev_date_added":null,"published":"2018-12-28"},{"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A pre-installed Android app allows any local application to trigger a factory reset without permissions, causing total data loss.","url":"https://insights.sbomify.com/CVE-2018-14999/"}