{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-32575 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-32575 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-32575 is a medium-severity memory corruption vulnerability in Intel(R) Trace Analyzer and Collector software, published on 16 Feb 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-32575 and fix it if it is affected.\n\nWhat it is: CVE-2022-32575 is a medium-severity memory corruption vulnerability in Intel(R) Trace Analyzer and Collector software, published on 16 Feb 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: There is no known exploitation of CVE-2022-32575 in the wild and no public exploit code.\n\nAffected product: Intel(R) Trace Analyzer and Collector software. 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-32575/ (Markdown: https://insights.sbomify.com/CVE-2022-32575/index.md)","id":"CVE-2022-32575","markdown":"https://insights.sbomify.com/CVE-2022-32575/index.md","name":"CVE-2022-32575","record":{"aliases":["GHSA-6rp7-j84j-5hw3"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Intel Trace Analyzer","requires_auth":"low_privilege","summary":"An authenticated local attacker can exploit an out-of-bounds write in Intel Trace Analyzer to escalate privileges.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"intel","cpe":[{"product":"trace_analyzer_and_collector","vendor":"intel"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out-of-bounds write in the Intel(R) Trace Analyzer and Collector software before version 2021.5 may allow an authenticated user to potentially enable escalation of privilege via local access.","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 Intel(R) Trace Analyzer and Collector software","id":"CVE-2022-32575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Intel(R) Unite(R) Plugin SDK","id":"CVE-2022-32576"},"packages":[],"prev":{"headline":"Use after free in iota All-In-One Security Kit","id":"CVE-2022-32574"},"products":["Intel(R) Trace Analyzer and Collector software"],"published":"2023-02-16","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Intel(R) FPGA OPAE Driver for Linux","id":"CVE-2020-24485","kev_date_added":null,"published":"2021-02-17"},{"cvss_score":6.7,"headline":"Privilege escalation in Intel(R) Trace Analyzer and Collector","id":"CVE-2023-31197","kev_date_added":null,"published":"2023-05-12"},{"cvss_score":6.7,"headline":"Privilege escalation in Intel(R) Trace Analyzer and Collector for Intel(R) oneAPI HPC Toolkit","id":"CVE-2022-26062","kev_date_added":null,"published":"2023-02-16"},{"cvss_score":5.5,"headline":"Denial of service in Intel(R) Trace Analyzer and Collector","id":"CVE-2022-21133","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":5.5,"headline":"Null dereference in Intel(R) Trace Analyzer and Collector","id":"CVE-2022-21156","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":5.5,"headline":"Information disclosure in Intel(R) Trace Analyzer and Collector","id":"CVE-2022-21218","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":5.5,"headline":"Information disclosure in Intel(R) Trace Analyzer and Collector","id":"CVE-2022-21226","kev_date_added":null,"published":"2022-02-09"}],"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-01-27","vendors":["n/a"]},"summary":"An authenticated local attacker can exploit an out-of-bounds write in Intel Trace Analyzer to escalate privileges.","url":"https://insights.sbomify.com/CVE-2022-32575/"}