{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6200 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6200 is a high-severity cross-site scripting vulnerability in HaloITSM, published on 6 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-6200 and fix it if it is affected.\n\nWhat it is: CVE-2024-6200 is a high-severity cross-site scripting vulnerability in HaloITSM, published on 6 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-6200 in the wild and no public exploit code.\n\nAffected product: HaloITSM. 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-2024-6200/ (Markdown: https://insights.sbomify.com/CVE-2024-6200/index.md)","id":"CVE-2024-6200","markdown":"https://insights.sbomify.com/CVE-2024-6200/index.md","name":"CVE-2024-6200","record":{"aliases":["GHSA-59j7-j82m-4gmq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"ITSM software","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts into tickets, allowing arbitrary actions on behalf of users viewing the ticket.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[{"product":"haloitsm","vendor":"haloservicesolutions"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"HaloITSM versions up to 2.146.1 are affected by a Stored Cross-Site Scripting (XSS) vulnerability. The injected JavaScript code can execute arbitrary action on behalf of the user accessing a ticket. HaloITSM versions past 2.146.1 (and patches starting from 2.143.61 ) fix the mentioned vulnerability.","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":"HaloITSM - Stored Cross-Site Scripting in Tickets","id":"CVE-2024-6200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"HaloITSM - Emailing Template Injection","id":"CVE-2024-6201"},"packages":[],"prev":{"headline":"Unauthenticated Remote Code Execution","id":"CVE-2024-6199"},"products":["HaloITSM"],"published":"2024-08-06","related":[{"cvss_score":9.8,"headline":"HaloITSM - SAML XML Signature Wrapping (XSW)","id":"CVE-2024-6202","kev_date_added":null,"published":"2024-08-06"},{"cvss_score":8.3,"headline":"HaloITSM - Password Reset Poisoning","id":"CVE-2024-6203","kev_date_added":null,"published":"2024-08-06"},{"cvss_score":5.3,"headline":"HaloITSM - Emailing Template Injection","id":"CVE-2024-6201","kev_date_added":null,"published":"2024-08-06"}],"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":"total"},"state":"PUBLISHED","updated":"2024-08-08","vendors":["Halo Service Solutions"]},"summary":"Attackers can inject malicious scripts into tickets, allowing arbitrary actions on behalf of users viewing the ticket.","url":"https://insights.sbomify.com/CVE-2024-6200/"}