Low (2.7) in Mitel MiCollab. In CISA KEV since 2025-01-07, with known ransomware use. EPSS 38% estimated probability of exploitation activity in the next 30 days.
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 the admin access level, and the disclosure is limited to non-sensitive system information. This vulnerability does not allow file modification or privilege escalation.
Severity
CVSS 3.1
2.7 low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS
38%(unchanged from 38% a week ago; 38% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-01-07, due 2025-01-28, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: partial, assessed 2025-01-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
Show the promptExplain CVE-2024-55550 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-55550?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-55550?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-55550 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.