CVE-2024-6201

5.3 MEDIUM

📋 TL;DR

HaloITSM versions up to 2.146.1 contain a template injection vulnerability in the email generation engine that allows attackers to execute arbitrary code in email templates. This can lead to sensitive information disclosure from the HaloITSM system. Organizations using affected versions of HaloITSM are vulnerable.

💻 Affected Systems

Products:
  • HaloITSM
Versions: Versions up to 2.146.1
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All installations using the default email template engine are affected. Patches starting from version 2.143.61 address the vulnerability.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise through remote code execution leading to complete data exfiltration, privilege escalation, and lateral movement within the network.

🟠

Likely Case

Sensitive information leakage including user credentials, configuration data, and potentially customer information stored in the HaloITSM system.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls preventing exploitation attempts from reaching vulnerable systems.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires access to email template functionality, which typically requires authenticated access. The vulnerability is in the template rendering engine.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.146.1 and later, or patches starting from 2.143.61

Vendor Advisory: https://haloitsm.com/guides/article/?kbid=2153

Restart Required: Yes

Instructions:

1. Backup your HaloITSM installation and database. 2. Download the latest version from the vendor portal. 3. Apply the update following HaloITSM's upgrade documentation. 4. Restart the HaloITSM service. 5. Verify the update was successful.

🔧 Temporary Workarounds

Disable email template editing

all

Restrict access to email template editing functionality to prevent injection attempts

Network segmentation

all

Isolate HaloITSM servers from untrusted networks and implement strict firewall rules

🧯 If You Can't Patch

  • Implement strict access controls to limit who can create or modify email templates
  • Monitor email generation logs for suspicious template injection patterns

🔍 How to Verify

Check if Vulnerable:

Check HaloITSM version in admin panel or via the web interface. Versions below 2.146.1 are vulnerable unless patched with 2.143.61 or later patches.

Check Version:

Check via HaloITSM web interface: Admin → System → About, or check application files for version information.

Verify Fix Applied:

Verify version is 2.146.1 or higher, or confirm patch version 2.143.61 or later is applied. Test email template functionality to ensure proper sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual email template modifications
  • Suspicious template syntax in email generation logs
  • Multiple failed template rendering attempts

Network Indicators:

  • Unusual outbound connections from HaloITSM server following email generation
  • Traffic patterns suggesting data exfiltration

SIEM Query:

source="haloitsm" AND (event="template_error" OR event="email_generation_failed" OR message="*template*injection*")

🔗 References

📤 Share & Export