{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10370 is a high-severity vulnerability in n/a, published on 11 May 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-2016-10370 and fix it if it is affected.\n\nWhat it is: CVE-2016-10370 is a high-severity vulnerability in n/a, published on 11 May 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-2016-10370 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-2016-10370/ (Markdown: https://insights.sbomify.com/CVE-2016-10370/index.md)","id":"CVE-2016-10370","markdown":"https://insights.sbomify.com/CVE-2016-10370/index.md","name":"CVE-2016-10370","record":{"aliases":["GHSA-9c6w-x974-x348"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OnePlus OTA Updater","requires_auth":"none","summary":"The OnePlus OTA Updater uses HTTP instead of TLS, increasing attack surface and enabling remote exploitation of other vulnerabilities.","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":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue was discovered on OnePlus devices such as the 3T. The OnePlus OTA Updater pushes the signed-OTA image over HTTP without TLS. While it does not allow for installation of arbitrary OTAs (due to the digital signature), it unnecessarily increases the attack surface, and allows for remote exploitation of other vulnerabilities such as CVE-2017-5948, CVE-2017-8850, and CVE-2017-8851.","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-2016-10370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2016-10371"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2016-10369"},"products":["n/a"],"published":"2017-05-11","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-5624","kev_date_added":null,"published":"2017-03-12"},{"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":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-06","vendors":["n/a"]},"summary":"The OnePlus OTA Updater uses HTTP instead of TLS, increasing attack surface and enabling remote exploitation of other vulnerabilities.","url":"https://insights.sbomify.com/CVE-2016-10370/"}