{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28973 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28973 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28973 is a high-severity authentication bypass vulnerability in n/a, published on 21 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28973 and fix it if it is affected.\n\nWhat it is: CVE-2020-28973 is a high-severity authentication bypass vulnerability in n/a, published on 21 Apr 2021. 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-2020-28973 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-2020-28973/ (Markdown: https://insights.sbomify.com/CVE-2020-28973/index.md)","id":"CVE-2020-28973","markdown":"https://insights.sbomify.com/CVE-2020-28973/index.md","name":"CVE-2020-28973","record":{"aliases":["GHSA-x3ww-q5hj-x9cc"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wireless alarm system","requires_auth":"none","summary":"Attackers can bypass authentication on the ABUS Secvest alarm system to steal credentials and disable the security system.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"secvest_wireless_alarm_system_fuaa50000_firmware","vendor":"abus"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The ABUS Secvest wireless alarm system FUAA50000 (v3.01.17) fails to properly authenticate some requests to its built-in HTTPS interface. Someone can use this vulnerability to obtain sensitive information from the system, such as usernames and passwords. This information can then be used to reconfigure or disable the alarm system.","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":"Auth bypass in n/a","id":"CVE-2020-28973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-28974"},"packages":[],"prev":{"headline":"SaltStack Salt Improper Certificate Validation","id":"CVE-2020-28972"},"products":["n/a"],"published":"2021-04-21","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":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":"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 bypass authentication on the ABUS Secvest alarm system to steal credentials and disable the security system.","url":"https://insights.sbomify.com/CVE-2020-28973/"}