haloitsm vulnerabilities and fixes
Recent CVEs affecting haloitsm, with upgrade or downgrade steps. 4 tracked.
haloitsm has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2024-08-06. Highest priority: CVE-2024-6202 (score 50/100).
- CVE-2024-6203 HIGH 8.3 UPGRADE HaloITSM versions up to 2.146.1 are affected by a Password Reset Poisoning vulnerability
- CVE-2024-6202 CRITICAL 9.8 UPGRADE HaloITSM versions up to 2.146.1 are affected by a SAML XML Signature Wrapping (XSW) vulnerability
- CVE-2024-6201 MEDIUM 5.3 UPGRADE HaloITSM versions up to 2.146.1 are affected by a Template Injection vulnerability within the engine used to g
- CVE-2024-6200 HIGH 8.0 UPGRADE HaloITSM versions up to 2.146.1 are affected by a Stored Cross-Site Scripting (XSS) vulnerability
FAQ
How do I fix haloitsm vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is haloitsm being exploited right now?
None of the tracked haloitsm CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which haloitsm CVE should I patch first?
CVE-2024-6202 currently ranks highest (50/100): HaloITSM versions up to 2.146.1 are affected by a SAML XML Signature Wrapping (XSW) vulnerability.