{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2652 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-2652 is a high-severity vulnerability in umlaeute/v4l2loopback, published on 4 Aug 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-2652 and fix it if it is affected.\n\nWhat it is: CVE-2022-2652 is a high-severity vulnerability in umlaeute/v4l2loopback, published on 4 Aug 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-2652 in the wild and no public exploit code.\n\nAffected product: umlaeute/v4l2loopback. 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-2652/ (Markdown: https://insights.sbomify.com/CVE-2022-2652/index.md)","id":"CVE-2022-2652","markdown":"https://insights.sbomify.com/CVE-2022-2652/index.md","name":"CVE-2022-2652","record":{"aliases":["DEBIAN-CVE-2022-2652","GHSA-grx9-955g-vjfg","UBUNTU-CVE-2022-2652","openSUSE-SU-2022:10159-1","openSUSE-SU-2022:10160-1","openSUSE-SU-2024:12372-1"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel module","requires_auth":"high_privilege","summary":"Crafted format strings in v4l2loopback card labels allow attackers to leak kernel stack memory and cause denial of service via module crashes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"v4l2loopback","vendor":"v4l2loopback_project"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"description":"Depending on the way the format strings in the card label are crafted it's possible to leak kernel stack memory. There is also the possibility for DoS due to the v4l2loopback kernel module crashing when providing the card label on request (reproduce e.g. with many %s modifiers in a row).","ecosystems":["openSUSE:Leap 15.3","openSUSE:Leap 15.4"],"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":"Use of Externally-Controlled Format String in umlaeute/v4l2loopback","id":"CVE-2022-2652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Path Traversal in plankanban/planka","id":"CVE-2022-2653"},"packages":[{"ecosystem":"openSUSE:Leap 15.3","fixed":["0.12.5-lp153.2.5.1"],"introduced":["0"],"last_affected":[],"package":"v4l2loopback","purl":"pkg:rpm/opensuse/v4l2loopback\u0026distro=openSUSE%20Leap%2015.3","source":"openSUSE-SU-2022:10160-1"},{"ecosystem":"openSUSE:Leap 15.4","fixed":["0.12.5-lp154.3.3.1"],"introduced":["0"],"last_affected":[],"package":"v4l2loopback","purl":"pkg:rpm/opensuse/v4l2loopback\u0026distro=openSUSE%20Leap%2015.4","source":"openSUSE-SU-2022:10159-1"}],"prev":{"headline":"Authentication Bypass by Primary Weakness in bookwyrm-social/bookwyrm","id":"CVE-2022-2651"},"products":["umlaeute/v4l2loopback"],"published":"2022-08-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":["umlaeute"]},"summary":"Crafted format strings in v4l2loopback card labels allow attackers to leak kernel stack memory and cause denial of service via module crashes.","url":"https://insights.sbomify.com/CVE-2022-2652/"}