{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6203 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6203 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6203 is a high-severity authentication bypass vulnerability in HaloITSM, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-6203 and fix it if it is affected.\n\nWhat it is: CVE-2024-6203 is a high-severity authentication bypass vulnerability in HaloITSM, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-6203 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-6203/ (Markdown: https://insights.sbomify.com/CVE-2024-6203/index.md)","id":"CVE-2024-6203","markdown":"https://insights.sbomify.com/CVE-2024-6203/index.md","name":"CVE-2024-6203","record":{"aliases":["GHSA-q664-v9r4-qmrg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"ITSM software","requires_auth":"none","summary":"Attackers can poison password reset links to leak tokens and take over user accounts in HaloITSM.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[{"product":"haloitsm","vendor":"haloservicesolutions"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"}],"description":"HaloITSM versions up to 2.146.1 are affected by a Password Reset Poisoning vulnerability. Poisoned password reset links can be sent to existing HaloITSM users (given their email address is known). When these poisoned links get accessed (e.g. manually by the victim or automatically by an email client software), the password reset token is leaked to the malicious actor, allowing them to set a new password for the victim's account.This potentially leads to account takeover attacks.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 - Password Reset Poisoning","id":"CVE-2024-6203","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection","id":"CVE-2024-6204"},"packages":[],"prev":{"headline":"HaloITSM - SAML XML Signature Wrapping (XSW)","id":"CVE-2024-6202"},"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,"headline":"HaloITSM - Stored Cross-Site Scripting in Tickets","id":"CVE-2024-6200","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-06","vendors":["Halo Service Solutions"]},"summary":"Attackers can poison password reset links to leak tokens and take over user accounts in HaloITSM.","url":"https://insights.sbomify.com/CVE-2024-6203/"}