{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22098 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22098 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22098 is a high-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 2 Sep 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-22098 and fix it if it is affected.\n\nWhat it is: CVE-2022-22098 is a high-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 2 Sep 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-22098 in the wild and no public exploit code.\n\nAffected product: Qualcomm Apq8096au Firmware. 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-22098/ (Markdown: https://insights.sbomify.com/CVE-2022-22098/index.md)","id":"CVE-2022-22098","markdown":"https://insights.sbomify.com/CVE-2022-22098/index.md","name":"CVE-2022-22098","record":{"aliases":["GHSA-wq26-v5hg-c2fr"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Snapdragon Auto firmware","requires_auth":"none","summary":"Memory corruption in Snapdragon Auto multimedia driver allows attackers to execute arbitrary code or escalate privileges via socket data.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"apq8096au_firmware","vendor":"qualcomm"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Memory corruption in multimedia driver due to untrusted pointer dereference while reading data from socket in Snapdragon Auto","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":"Memory corruption in Snapdragon Auto","id":"CVE-2022-22098","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:apq8096au_firmware","products":["qualcomm:apq8096au_firmware"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Snapdragon Auto","id":"CVE-2022-22099"},"packages":[],"prev":{"headline":"Use after free in Snapdragon Consumer IOT","id":"CVE-2022-22097"},"products":["Snapdragon Auto"],"published":"2022-09-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile","id":"CVE-2019-14045","kev_date_added":null,"published":"2020-03-05"},{"cvss_score":9.8,"headline":"Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile","id":"CVE-2017-14911","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.1,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-11126","kev_date_added":null,"published":"2021-06-09"},{"cvss_score":8.4,"headline":"Improper access control in Qualcomm IPC","id":"CVE-2022-33243","kev_date_added":null,"published":"2023-02-09"},{"cvss_score":8.4,"headline":"Memory corruption in Core","id":"CVE-2022-22063","kev_date_added":null,"published":"2022-12-14"},{"cvss_score":8.4,"headline":"Memory corruption in Snapdragon Auto","id":"CVE-2022-22100","kev_date_added":null,"published":"2022-09-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":["Qualcomm, Inc."]},"summary":"Memory corruption in Snapdragon Auto multimedia driver allows attackers to execute arbitrary code or escalate privileges via socket data.","url":"https://insights.sbomify.com/CVE-2022-22098/"}