{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19441 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19441 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19441 is a medium-severity vulnerability in n/a, published on 27 Jan 2020. 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-19441 and fix it if it is affected.\n\nWhat it is: CVE-2018-19441 is a medium-severity vulnerability in n/a, published on 27 Jan 2020. 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-19441 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-19441/ (Markdown: https://insights.sbomify.com/CVE-2018-19441/index.md)","id":"CVE-2018-19441","markdown":"https://insights.sbomify.com/CVE-2018-19441/index.md","name":"CVE-2018-19441","record":{"aliases":["GHSA-4f4h-4mvr-gm9g"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Neato Botvac robot","requires_auth":"low_privilege","summary":"Attackers can brute force robot secret keys due to weak random number generation, enabling unauthorized access to local and cloud authentication.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"botvac_connected_firmware","vendor":"neatorobotics"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"An issue was discovered in Neato Botvac Connected 2.2.0. The GenerateRobotPassword function of the NeatoCrypto library generates insufficiently random numbers for robot secret_key values used for local and cloud authentication/authorization. If an attacker knows the serial number and is able to estimate the time of first provisioning of a robot, he is able to brute force the generated secret_key of the robot. This is because the entropy of the secret_key exclusively relies on these two values, due to not seeding the random generator and using several constant inputs for secret_key computation. Serial numbers are printed on the packaging and equal the MAC address of the robot.","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":"Weak cryptography in n/a","id":"CVE-2018-19441","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-19442"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-19440"},"products":["n/a"],"published":"2020-01-27","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-19442","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2018-18638","kev_date_added":null,"published":"2018-10-24"},{"cvss_score":7.4,"headline":"Security feature bypass in n/a","id":"CVE-2018-20785","kev_date_added":null,"published":"2019-02-23"}],"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 brute force robot secret keys due to weak random number generation, enabling unauthorized access to local and cloud authentication.","url":"https://insights.sbomify.com/CVE-2018-19441/"}