CVE-2024-41713: Mitel MiCollab Path Traversal Vulnerability
Mitel · MiCollab · NVD published 2024-10-22 · posted 2025-01-07 · last modified 2026-08-04
What it is
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could allow an unauthenticated attacker to conduct a path traversal attack, due to insufficient input validation. A successful exploit could allow unauthorized access, enabling the attacker to view, corrupt, or delete users' data and system configurations.
| Weakness | CWE-22 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (source: [email protected]) |
| CISA due date | 2025-01-28 (for US federal agencies under BOD; a good deadline for everyone) |
| ATT&CK tactics | Privilege Escalation → Collection |
Exploitation evidence
First exploit evidence seen: 2024-12-05 (earliest date across the sources below).
Exploited in the wild
- CISA KEV: listed since 2025-01-07. Source
Public exploit code
GitHub proof-of-concept repositories
5 public repositories from 5 accounts, first seen 2024-12-05. Most starred: watchtowrlabs/Mitel-MiCollab-Auth-Bypass_CVE-2024-41713 (20 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: CISA KEV · nomi-sec/PoC-in-GitHub.
Defend the Chain
The attack chain for CVE-2024-41713 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1068 Exploitation for Privilege Escalation CTID: exploitation technique
This path traversal vulnerability can lead to privilege escalation on MiCollab, which can then lead to other exploits such as CVE-2024-55550.
How to fix it
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)
Fixed versions
- mitel micollab: versions up to and including 9.8.1.201 are affected; check the vendor advisory for the fixed release.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://www.mitel.com/support/security-advisories/mitel-product-security-advisory-misa-2024-0029 (CISA KEV notes)
MITRE ATT&CK mitigations for this chain
- M1051 Update Software (for T1068) : Update software regularly by employing patch management for internal enterprise endpoints and servers.
- M1050 Exploit Protection (for T1068) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
- M1048 Application Isolation and Sandboxing (for T1068) : Make it difficult for adversaries to advance their operation through exploitation of undiscovered or unpatched vulnerabilities by using sandboxing. Other types of virtualization and application microsegmentation may also mitigate the impact of some types of exploitation. Risks of additional exploits and weaknesses in t
- M1019 Threat Intelligence Program (for T1068) : Develop a robust cyber threat intelligence capability to determine what types and levels of threat may use software exploits and 0-days against a particular organization.
- M1038 Execution Prevention (for T1068) : Consider blocking the execution of known vulnerable drivers that adversaries may exploit to execute code in kernel mode. Validate driver block rules in audit mode to ensure stability prior to production deployment.
- M1057 Data Loss Prevention (for T1005) : Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.
Detection Generic guidance
- Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and on exploitation crashes of privileged services.
- Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.