{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8267 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8267 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8267 is a medium-severity authentication bypass vulnerability in UniFi Protect, published on 5 Nov 2020. 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-8267 and fix it if it is affected.\n\nWhat it is: CVE-2020-8267 is a medium-severity authentication bypass vulnerability in UniFi Protect, published on 5 Nov 2020. 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-8267 in the wild and no public exploit code.\n\nAffected product: UniFi Protect. 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-8267/ (Markdown: https://insights.sbomify.com/CVE-2020-8267/index.md)","id":"CVE-2020-8267","markdown":"https://insights.sbomify.com/CVE-2020-8267/index.md","name":"CVE-2020-8267","record":{"aliases":["GHSA-qhjp-4vc3-896g"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"UniFi Protect controller","requires_auth":"none","summary":"Attackers can bypass authentication in the UniFi Protect controller API by improperly using the x-token header, allowing unauthorized access to authenticated messages.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"unifi_protect_firmware","vendor":"ui"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"A security issue was found in UniFi Protect controller v1.14.10 and earlier.The authentication in the UniFi Protect controller API was using “x-token” improperly, allowing attackers to use the API to send authenticated messages without a valid token.This vulnerability was fixed in UniFi Protect v1.14.11 and newer.This issue does not impact UniFi Cloud Key Gen 2 plus.This issue does not impact UDM-Pro customers with UniFi Protect stopped.Affected Products:UDM-Pro firmware 1.7.2 and earlier.UNVR firmware 1.3.12 and earlier.Mitigation:Update UniFi Protect to v1.14.11 or newer version; the UniFi Protect controller can be updated through your UniFi OS settings.Alternatively, you can update UNVR and UDM-Pro to:- UNVR firmware to 1.3.15 or newer.- UDM-Pro firmware to 1.8.0 or newer.","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 UniFi Protect","id":"CVE-2020-8267","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Prototype pollution in json8-merge-patch","id":"CVE-2020-8268"},"packages":[],"prev":{"headline":"Use after free in Node","id":"CVE-2020-8265"},"products":["UniFi Protect"],"published":"2020-11-05","related":[{"cvss_score":8.8,"headline":"Command injection in Protect for UniFi Cloud Key Gen2 Plus, UniFi Dream Machine Pro, UNVR","id":"CVE-2020-8188","kev_date_added":null,"published":"2020-07-02"}],"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 in the UniFi Protect controller API by improperly using the x-token header, allowing unauthorized access to authenticated messages.","url":"https://insights.sbomify.com/CVE-2020-8267/"}