{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-9863 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9863 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9863 is a critical vulnerability in n/a, published on 27 Mar 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-9863 and fix it if it is affected.\n\nWhat it is: CVE-2019-9863 is a critical vulnerability in n/a, published on 27 Mar 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-9863 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-9863/ (Markdown: https://insights.sbomify.com/CVE-2019-9863/index.md)","id":"CVE-2019-9863","markdown":"https://insights.sbomify.com/CVE-2019-9863/index.md","name":"CVE-2019-9863","record":{"aliases":["GHSA-v2mr-5m5h-xvcr"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wireless alarm system","requires_auth":"none","summary":"An attacker can predict rolling codes to remotely control the alarm system due to an insecure cryptographic algorithm.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"secvest_wireless_alarm_system_fuaa50000_firmware","vendor":"abus"},{"product":"secvest_wireless_remote_control_fube50014_firmware","vendor":"abus"},{"product":"secvest_wireless_remote_control_fube50015_firmware","vendor":"abus"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"Due to the use of an insecure algorithm for rolling codes in the ABUS Secvest wireless alarm system FUAA50000 3.01.01 and its remote controls FUBE50014 and FUBE50015, an attacker is able to predict valid future rolling codes, and can thus remotely control the alarm system in an unauthorized way.","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-2019-9863","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2019-9864"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-9862"},"products":["n/a"],"published":"2019-03-27","related":[{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2019-9861","kev_date_added":null,"published":"2019-05-14"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2020-28973","kev_date_added":null,"published":"2021-04-21"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2019-14261","kev_date_added":null,"published":"2019-09-03"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2019-9860","kev_date_added":null,"published":"2019-03-27"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2019-9862","kev_date_added":null,"published":"2019-03-27"}],"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":"An attacker can predict rolling codes to remotely control the alarm system due to an insecure cryptographic algorithm.","url":"https://insights.sbomify.com/CVE-2019-9863/"}