{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5622 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5622 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5622 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Mar 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-5622 and fix it if it is affected.\n\nWhat it is: CVE-2017-5622 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Mar 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-5622 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-5622/ (Markdown: https://insights.sbomify.com/CVE-2017-5622/index.md)","id":"CVE-2017-5622","markdown":"https://insights.sbomify.com/CVE-2017-5622/index.md","name":"CVE-2017-5622","record":{"aliases":["GHSA-pwjc-cjmg-4g8f"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OnePlus Android OS","requires_auth":"low_privilege","summary":"A physical attacker can connect a malicious charger to a powered-off OnePlus device to enable ADB without authorization, allowing data exfiltration or further exploitation.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oxygenos","vendor":"oneplus"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"With OxygenOS before 4.0.3, when a charger is connected to a powered-off OnePlus 3 or 3T device, the platform starts with adbd enabled. Therefore, a malicious charger or a physical attacker can open up, without authorization, an ADB session with the device, in order to further exploit other vulnerabilities and/or exfiltrate sensitive information.","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":"Auth bypass in n/a","id":"CVE-2017-5622","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2017-5623"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-5621"},"products":["n/a"],"published":"2017-03-26","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":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":"A physical attacker can connect a malicious charger to a powered-off OnePlus device to enable ADB without authorization, allowing data exfiltration or further exploitation.","url":"https://insights.sbomify.com/CVE-2017-5622/"}