{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-42878 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-42878 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-42878 is a low-severity vulnerability in Intel(R) Trace Analyzer and Collector software, published on 10 May 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-42878 and fix it if it is affected.\n\nWhat it is: CVE-2022-42878 is a low-severity vulnerability in Intel(R) Trace Analyzer and Collector software, published on 10 May 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-42878 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-42878/ (Markdown: https://insights.sbomify.com/CVE-2022-42878/index.md)","id":"CVE-2022-42878","markdown":"https://insights.sbomify.com/CVE-2022-42878/index.md","name":"CVE-2022-42878","record":{"aliases":["GHSA-c8h7-rw5f-pm89"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Intel Trace Analyzer","requires_auth":"low_privilege","summary":"An authenticated local user can trigger a null pointer dereference in Intel Trace Analyzer to disclose sensitive information.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"intel","cpe":[{"product":"oneapi_hpc_toolkit","vendor":"intel"},{"product":"trace_analyzer_and_collector","vendor":"intel"}],"cvss":{"score":2.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"},{"id":"CWE-395","name":"Use of NullPointerException Catch to Detect NULL Pointer Dereference"}],"description":"Null pointer dereference for some Intel(R) Trace Analyzer and Collector software before version 2021.8.0 published Dec 2022 may allow an authenticated user to potentially enable information disclosure 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":"Null dereference in Intel(R) Trace Analyzer and Collector software","id":"CVE-2022-42878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in Intel(R) Arc(TM) Control software","id":"CVE-2022-42879"},"packages":[],"prev":{"headline":"Use after free in tvOS","id":"CVE-2022-42867"},"products":["Intel(R) Trace Analyzer and Collector software"],"published":"2023-05-10","related":[{"cvss_score":7.8,"headline":"Memory corruption in Intel(R) Trace Analyzer and Collector software","id":"CVE-2023-23569","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":5.4,"headline":"Privilege escalation in Intel(R) Trace Analyzer and Collector software","id":"CVE-2024-28172","kev_date_added":null,"published":"2024-08-14"},{"cvss_score":4.8,"headline":"Memory corruption in Intel(R) Trace Analyzer and Collector software","id":"CVE-2023-23580","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":3.9,"headline":"Memory corruption in Intel(R) Trace Analyzer and Collector software","id":"CVE-2023-23910","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":2.8,"headline":"Information disclosure in Intel(R) Trace Analyzer and Collector software","id":"CVE-2023-23909","kev_date_added":null,"published":"2023-05-10"}],"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 user can trigger a null pointer dereference in Intel Trace Analyzer to disclose sensitive information.","url":"https://insights.sbomify.com/CVE-2022-42878/"}