CVE-2024-55550
Path Traversal in Mitel Micollab ≤ 9.8.1.201
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-55550 is a low-severity Path Traversal (CWE-22) vulnerability in Mitel Micollab. Its CVSS base score is 2.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Mitel MiCollab through version 9.8 SP2 contains a path traversal vulnerability (CWE-22) that stems from insufficient input sanitization. An authenticated administrative user can supply crafted input to read arbitrary local files on the affected system. The flaw is rated CVSS 2.7 and permits access only to non-sensitive system information within the administrator’s existing privilege level; it does not enable file modification or privilege escalation.
An attacker who already possesses administrative credentials can exploit the issue over the network to retrieve files that would otherwise be inaccessible through normal administrative interfaces. Because the vulnerability requires high privileges, the attack surface is limited to insiders or compromised admin accounts, and successful exploitation yields only read access to constrained, non-sensitive resources.
Mitel has published security advisory MISA-2024-0029, available alongside general product security updates at mitel.com/support/security-advisories, that addresses the flaw. The advisory outlines the affected releases and directs administrators to apply the vendor-supplied remediation.
The CVE appears in CISA’s Known Exploited Vulnerabilities catalog, confirming observed in-the-wild exploitation. Its EPSS score rose from a low baseline after disclosure to a peak of 0.4272 on 2025-01-09 before receding to the current value of 0.1772, indicating a measurable increase in exploitation interest following public release.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52803
Vulnerability Data
Mitel MiCollab through 9.8 SP2 could allow an authenticated attacker with administrative privilege to conduct a local file read, due to insufficient input sanitization. A successful exploit could allow the authenticated admin attacker to access resources that are constrained to…
more
the admin access level, and the disclosure is limited to non-sensitive system information. This vulnerability does not allow file modification or privilege escalation.
- CWE(s)
- KEV Date Added
- 07 January 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.