{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9861 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9861 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9861 is a high-severity vulnerability in n/a, published on 14 May 2019. 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-2019-9861 and fix it if it is affected.\n\nWhat it is: CVE-2019-9861 is a high-severity vulnerability in n/a, published on 14 May 2019. 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-2019-9861 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-9861/ (Markdown: https://insights.sbomify.com/CVE-2019-9861/index.md)","id":"CVE-2019-9861","markdown":"https://insights.sbomify.com/CVE-2019-9861/index.md","name":"CVE-2019-9861","record":{"aliases":["GHSA-mjxp-pfh5-29xr"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"wireless alarm system","requires_auth":"none","summary":"Attackers can clone RFID keys to bypass security and deactivate the alarm system due to insecure MIFARE Classic technology.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"secvest_wireless_alarm_system_fuaa50000_firmware","vendor":"abus"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"Due to the use of an insecure RFID technology (MIFARE Classic), ABUS proximity chip keys (RFID tokens) of the ABUS Secvest FUAA50000 wireless alarm system can easily be cloned and used to deactivate 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":"Security feature bypass in n/a","id":"CVE-2019-9861","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-9862"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2019-9860"},"products":["n/a"],"published":"2019-05-14","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2019-9863","kev_date_added":null,"published":"2019-03-27"},{"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":"Attackers can clone RFID keys to bypass security and deactivate the alarm system due to insecure MIFARE Classic technology.","url":"https://insights.sbomify.com/CVE-2019-9861/"}