{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5624 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5624 is a critical vulnerability in n/a, published on 12 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-5624 and fix it if it is affected.\n\nWhat it is: CVE-2017-5624 is a critical vulnerability in n/a, published on 12 Mar 2017. 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-2017-5624 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-2017-5624/ (Markdown: https://insights.sbomify.com/CVE-2017-5624/index.md)","id":"CVE-2017-5624","markdown":"https://insights.sbomify.com/CVE-2017-5624/index.md","name":"CVE-2017-5624","record":{"aliases":["GHSA-hhqp-73g9-vq23"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OnePlus OxygenOS","requires_auth":"none","summary":"Attackers can disable dm-verity via fastboot to bypass system integrity checks, enabling persistent code execution and privilege escalation on OnePlus devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oxygenos","vendor":"oneplus"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"An issue was discovered in OxygenOS before 4.0.3 for OnePlus 3 and 3T. The attacker can persistently make the (locked) bootloader start the platform with dm-verity disabled, by issuing the 'fastboot oem disable_dm_verity' command. Having dm-verity disabled, the kernel will not verify the system partition (and any other dm-verity protected partition), which may allow for persistent code execution and privilege escalation.","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":"Security feature bypass in n/a","id":"CVE-2017-5624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-5625"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2017-5623"},"products":["n/a"],"published":"2017-03-12","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-5626","kev_date_added":null,"published":"2017-03-12"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2017-5554","kev_date_added":null,"published":"2017-01-23"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2016-10370","kev_date_added":null,"published":"2017-05-11"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-5947","kev_date_added":null,"published":"2018-03-29"},{"cvss_score":6.6,"headline":"Security feature bypass in n/a","id":"CVE-2017-5623","kev_date_added":null,"published":"2017-03-19"},{"cvss_score":5.9,"headline":"Security feature bypass in n/a","id":"CVE-2017-5948","kev_date_added":null,"published":"2017-05-11"}],"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 can disable dm-verity via fastboot to bypass system integrity checks, enabling persistent code execution and privilege escalation on OnePlus devices.","url":"https://insights.sbomify.com/CVE-2017-5624/"}