{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-16242 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16242 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16242 is a medium-severity vulnerability in n/a, published on 14 Sep 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-16242 and fix it if it is affected.\n\nWhat it is: CVE-2018-16242 is a medium-severity vulnerability in n/a, published on 14 Sep 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-16242 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-16242/ (Markdown: https://insights.sbomify.com/CVE-2018-16242/index.md)","id":"CVE-2018-16242","markdown":"https://insights.sbomify.com/CVE-2018-16242/index.md","name":"CVE-2018-16242","record":{"aliases":["GHSA-2vpv-3c94-j6hf"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart bike locker","requires_auth":"none","summary":"Attackers can bypass bicycle locking mechanisms by replaying Bluetooth Low Energy ciphertext due to a predictable nonce in the smart locker protocol.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"obike-stationless_bike_sharing","vendor":"o.bike"},{"product":"smart_locker_firmware","vendor":"o.bike"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"oBike relies on Hangzhou Luoping Smart Locker to lock bicycles, which allows attackers to bypass the locking mechanism by using Bluetooth Low Energy (BLE) to replay ciphertext based on a predictable nonce used in the locking protocol.","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-2018-16242","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-16243"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2018-16239"},"products":["n/a"],"published":"2018-09-14","related":[],"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 bypass bicycle locking mechanisms by replaying Bluetooth Low Energy ciphertext due to a predictable nonce in the smart locker protocol.","url":"https://insights.sbomify.com/CVE-2018-16242/"}