{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23467 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2022-23467 is a medium-severity vulnerability in openrazer, published on 5 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-23467 and fix it if it is affected.\n\nWhat it is: CVE-2022-23467 is a medium-severity vulnerability in openrazer, published on 5 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-23467 in the wild and no public exploit code.\n\nAffected product: openrazer. 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-23467/ (Markdown: https://insights.sbomify.com/CVE-2022-23467/index.md)","id":"CVE-2022-23467","markdown":"https://insights.sbomify.com/CVE-2022-23467/index.md","name":"CVE-2022-23467","record":{"aliases":["DEBIAN-CVE-2022-23467","GHSA-39hg-jvc9-fg7h","UBUNTU-CVE-2022-23467"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux USB driver","requires_auth":"low_privilege","summary":"A local attacker with physical access can leak stack addresses via a modified USB device, potentially bypassing KASLR in the OpenRazer Linux driver.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openrazer","vendor":"openrazer_project"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"OpenRazer is an open source driver and user-space daemon to control Razer device lighting and other features on GNU/Linux. Using a modified USB device an attacker can leak stack addresses of the `razer_attr_read_dpi_stages`, potentially bypassing KASLR. To exploit this vulnerability an attacker would need to access to a users keyboard or mouse or would need to convince a user to use a modified device. The issue has been patched in v3.5.1. Users are advised to upgrade and should be reminded not to plug in unknown USB devices.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Out of Bounds Read in OpenRazer Driver","id":"CVE-2022-23467","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Buffer Overflow in xrdp","id":"CVE-2022-23468"},"packages":[],"prev":{"headline":"DOM-based cross-site scripting (XSS) in teler dashboard","id":"CVE-2022-23466"},"products":["openrazer"],"published":"2022-12-05","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-29021","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-29022","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-29023","kev_date_added":null,"published":"2022-05-20"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["openrazer"]},"summary":"A local attacker with physical access can leak stack addresses via a modified USB device, potentially bypassing KASLR in the OpenRazer Linux driver.","url":"https://insights.sbomify.com/CVE-2022-23467/"}