{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43293 exists.","fix":"No fix has been published for CVE-2022-43293 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-43293 is a medium-severity path traversal vulnerability in n/a, published on 11 Apr 2023. 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-43293 and fix it if it is affected.\n\nWhat it is: CVE-2022-43293 is a medium-severity path traversal vulnerability in n/a, published on 11 Apr 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43293 exists.\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-43293/ (Markdown: https://insights.sbomify.com/CVE-2022-43293/index.md)","id":"CVE-2022-43293","markdown":"https://insights.sbomify.com/CVE-2022-43293/index.md","name":"CVE-2022-43293","record":{"aliases":["GHSA-gj52-rqw6-xxqh"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wacom Tablet Driver","requires_auth":"none","summary":"An arbitrary file write vulnerability in the Wacom Tablet Driver allows attackers to execute code or escalate privileges via path traversal.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"driver","vendor":"wacom"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Wacom Driver 6.3.46-1 for Windows was discovered to contain an arbitrary file write vulnerability via the component \\Wacom\\Wacom_Tablet.exe.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-04-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-04-07T13:38:27Z","kind":"github_poc","ref":"https://github.com/LucaBarile/CVE-2022-43293","stars":0,"title":"Exploit and report for CVE-2022-43293"}],"tier":"weaponised"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2022-43293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-43294"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2022-43292"},"products":["n/a"],"published":"2023-04-11","related":[{"cvss_score":7.8,"headline":"Wacom Drivers for Windows Incorrect Permission Assignment Local Privilege Escalation Vulnerability","id":"CVE-2023-32162","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":7.8,"headline":"Wacom Drivers for Windows Link Following Local Privilege Escalation Vulnerability","id":"CVE-2023-32163","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":7.8,"headline":"Privilege escalation in Wacom","id":"CVE-2019-5012","kev_date_added":null,"published":"2019-10-24"},{"cvss_score":7.3,"headline":"Path traversal in n/a","id":"CVE-2022-38604","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.1,"headline":"Command injection in Wacom","id":"CVE-2019-5013","kev_date_added":null,"published":"2019-10-24"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-11","vendors":["n/a"]},"summary":"An arbitrary file write vulnerability in the Wacom Tablet Driver allows attackers to execute code or escalate privileges via path traversal.","url":"https://insights.sbomify.com/CVE-2022-43293/"}