{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-42335 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-42335 is a high-severity vulnerability in Fedoraproject Fedora, published on 25 Apr 2023. 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-42335 and fix it if it is affected.\n\nWhat it is: CVE-2022-42335 is a high-severity vulnerability in Fedoraproject Fedora, published on 25 Apr 2023. 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-42335 in the wild and no public exploit code.\n\nAffected product: Fedoraproject Fedora. 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-42335/ (Markdown: https://insights.sbomify.com/CVE-2022-42335/index.md)","id":"CVE-2022-42335","markdown":"https://insights.sbomify.com/CVE-2022-42335/index.md","name":"CVE-2022-42335","record":{"aliases":["ALPINE-CVE-2022-42335","DEBIAN-CVE-2022-42335","GHSA-pwx9-2gvj-242v","UBUNTU-CVE-2022-42335","openSUSE-SU-2024:12917-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"A guest with a passed-through PCI device can trigger an arbitrary pointer dereference in the Xen hypervisor, potentially causing a crash or code execution.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[{"product":"fedora","vendor":"fedoraproject"},{"product":"xen","vendor":"xen"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"x86 shadow paging arbitrary pointer dereference In environments where host assisted address translation is necessary but Hardware Assisted Paging (HAP) is unavailable, Xen will run guests in so called shadow mode. Due to too lax a check in one of the hypervisor routines used for shadow page handling it is possible for a guest with a PCI device passed through to cause the hypervisor to access an arbitrary pointer partially under guest control.","ecosystems":["openSUSE:Tumbleweed"],"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":"Null dereference in xen","id":"CVE-2022-42335","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fedoraproject:fedora","products":["fedoraproject:fedora","xen:xen"],"type":"null_dereference","year":"2022"},"n_packages":1,"n_references":5,"next":{"headline":"Security feature bypass in xen","id":"CVE-2022-42336"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["4.17.1_02-1.1"],"introduced":["0"],"last_affected":[],"package":"xen","purl":"pkg:rpm/opensuse/xen\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:12917-1"}],"prev":{"headline":"Race condition in xen","id":"CVE-2022-42334"},"products":["xen"],"published":"2023-04-25","related":[{"cvss_score":9.8,"headline":"PHP-CGI OS Command Injection","id":"CVE-2024-4577","kev_date_added":"2024-06-12","published":"2024-06-09"},{"cvss_score":9.8,"headline":"Grafana Authentication Bypass","id":"CVE-2021-39226","kev_date_added":"2022-08-25","published":"2021-10-05"},{"cvss_score":9.8,"headline":"VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow","id":"CVE-2019-5544","kev_date_added":"2021-11-03","published":"2019-12-06"},{"cvss_score":9.6,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2024-4947","kev_date_added":"2024-05-20","published":"2024-05-15"},{"cvss_score":9.6,"headline":"Google Chromium Visuals Use-After-Free","id":"CVE-2024-4671","kev_date_added":"2024-05-13","published":"2024-05-09"},{"cvss_score":9.6,"headline":"Google Chromium Mojo Insufficient Data Validation","id":"CVE-2022-3075","kev_date_added":"2022-09-08","published":"2022-09-26"},{"cvss_score":9.6,"headline":"Google Chromium Indexed DB API Use-After-Free","id":"CVE-2021-30633","kev_date_added":"2021-11-03","published":"2021-10-08"}],"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":["Xen"]},"summary":"A guest with a passed-through PCI device can trigger an arbitrary pointer dereference in the Xen hypervisor, potentially causing a crash or code execution.","url":"https://insights.sbomify.com/CVE-2022-42335/"}