{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12821 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12821 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12821 is a medium-severity vulnerability in n/a, published on 19 Jul 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-2019-12821 and fix it if it is affected.\n\nWhat it is: CVE-2019-12821 is a medium-severity vulnerability in n/a, published on 19 Jul 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-2019-12821 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-2019-12821/ (Markdown: https://insights.sbomify.com/CVE-2019-12821/index.md)","id":"CVE-2019-12821","markdown":"https://insights.sbomify.com/CVE-2019-12821/index.md","name":"CVE-2019-12821","record":{"aliases":["GHSA-fcfq-5mjg-9mh6"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"robot vacuum cleaner","requires_auth":"none","summary":"Attackers can hijack robot vacuums by predicting QR codes based on device IDs, gaining full control without authorization.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"i3_firmware","vendor":"jisiwei"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"A vulnerability was found in the app 2.0 of the Shenzhen Jisiwei i3 robot vacuum cleaner, while adding a device to the account using a QR-code. The QR-code follows an easily predictable pattern that depends only on the specific device ID of the robot vacuum cleaner. By generating a QR-code containing information about the device ID, it is possible to connect an arbitrary device and gain full access to it. The device ID has an initial \"JSW\" substring followed by a six digit number that depends on the specific device.","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-2019-12821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-12822"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-12820"},"products":["n/a"],"published":"2019-07-19","related":[{"cvss_score":5.6,"headline":"Information disclosure in n/a","id":"CVE-2019-12820","kev_date_added":null,"published":"2019-07-19"}],"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-04","vendors":["n/a"]},"summary":"Attackers can hijack robot vacuums by predicting QR codes based on device IDs, gaining full control without authorization.","url":"https://insights.sbomify.com/CVE-2019-12821/"}