{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31461 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-31461 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31461 is a high-severity authentication bypass vulnerability in n/a, published on 2 Jun 2022. 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-2022-31461 and fix it if it is affected.\n\nWhat it is: CVE-2022-31461 is a high-severity authentication bypass vulnerability in n/a, published on 2 Jun 2022. 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-2022-31461 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-2022-31461/ (Markdown: https://insights.sbomify.com/CVE-2022-31461/index.md)","id":"CVE-2022-31461","markdown":"https://insights.sbomify.com/CVE-2022-31461/index.md","name":"CVE-2022-31461","record":{"aliases":["GHSA-5295-4v9w-mwc9"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Meeting Owl device","requires_auth":"none","summary":"Attackers can bypass passcode protection on Meeting Owl devices by sending a specific message, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meeting_owl_pro_firmware","vendor":"owllabs"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:A/A:N/C:N/I:H/PR:N/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Owl Labs Meeting Owl 5.2.0.15 allows attackers to deactivate the passcode protection mechanism via a certain c 11 message.","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-2022-31461","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-31462"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-31460"},"products":["n/a"],"published":"2022-06-02","related":[{"cvss_score":9.3,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-31462","kev_date_added":null,"published":"2022-06-02"},{"cvss_score":8.2,"headline":"Auth bypass in n/a","id":"CVE-2022-31463","kev_date_added":null,"published":"2022-06-02"},{"cvss_score":7.4,"headline":"Information disclosure in n/a","id":"CVE-2022-31459","kev_date_added":null,"published":"2022-06-02"},{"cvss_score":7.4,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-31460","kev_date_added":null,"published":"2022-06-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-03","vendors":["n/a"]},"summary":"Attackers can bypass passcode protection on Meeting Owl devices by sending a specific message, allowing unauthorized access.","url":"https://insights.sbomify.com/CVE-2022-31461/"}