{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44905 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44905 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44905 is a high-severity missing authorization vulnerability in n/a, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-44905 and fix it if it is affected.\n\nWhat it is: CVE-2021-44905 is a high-severity missing authorization vulnerability in n/a, published on 25 Mar 2022. 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-2021-44905 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-2021-44905/ (Markdown: https://insights.sbomify.com/CVE-2021-44905/index.md)","id":"CVE-2021-44905","markdown":"https://insights.sbomify.com/CVE-2021-44905/index.md","name":"CVE-2021-44905","record":{"aliases":["GHSA-4gwv-wgh3-fxhf"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Smart Lock","requires_auth":"none","summary":"Remote attackers can disable the Fortessa smart lock by unauthenticated editing of the lock name due to incorrect Bluetooth service permissions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fortessa_ftbtld_firmware","vendor":"cef"}],"cvss":{"score":8.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"Incorrect permissions in the Bluetooth Services in the Fortessa FTBTLD Smart Lock as of 12-13-2022 allows a remote attacker to disable the lock via an unauthenticated edit to the lock name.","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":"Missing authorization in n/a","id":"CVE-2021-44905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Prototype Pollution in minimist","id":"CVE-2021-44906"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2021-44903"},"products":["n/a"],"published":"2022-03-25","related":[],"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":"Remote attackers can disable the Fortessa smart lock by unauthenticated editing of the lock name due to incorrect Bluetooth service permissions.","url":"https://insights.sbomify.com/CVE-2021-44905/"}