CriticalCVE-2024-41713

    Mitel MiCollab Path Traversal Vulnerability (CVE-2024-41713)

    Published In CISA KEV since Sources: NCSC NZ, pwn.watch, CVE.org

    What is affected, what to do

    The vulnerability CVE-2024-41713 allows an attacker to perform a path traversal attack to gain unauthorized access to the system. It can be chained with CVE-2024-55550, enabling an unauthenticated, remote attacker to read arbitrary files on the server. This vulnerability is actively exploited in ransomware campaigns since 2025 and affects the NuPoint Unified Messaging component of Mitel MiCollab up to version 9.8 SP1 FP2 (9.8.1.201). An immediate patch to the latest version is urgently required to ensure security.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Mitel MiCollab lte *..9.8.1.201

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.1

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: NCSC NZ, pwn.watch, CVE.org

    97.2 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.89

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    256.95 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: NCSC NZ How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    97.2 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.89
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw is network-reachable without authentication and without user interaction, affects a typically internet-exposed unified-communications component, and CISA has flagged it as used in ransomware campaigns — exploitation likelihood is among the highest in the KEV catalogue. Chained with CVE-2024-55550 it becomes a pre-auth arbitrary file read, delivering credential theft, lateral movement into the telephony estate and disruption of voice services. For NIS2-regulated organisations running MiCollab in the DMZ this is a P1 patch (within 24-72 h); where immediate patching is not possible, the interface must be removed from the public internet until the update is deployed.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Upgrade Mitel MiCollab to version 9.8 SP2 (9.8.2) or later without delay — all releases up to and including 9.8.1.201 (9.8 SP1 FP2) are vulnerable, and the NuPoint Unified Messaging (NPM) component is the affected module.
      • Restrict external reachability of the MiCollab web interface (typically TCP/443) immediately: place a reverse proxy, WAF or firewall ACL in front of the server and allow only known partner IPs, VPN pools and carrier SBCs until the patch is in production.
      • Retro-hunt MiCollab webserver access logs for the past 90 days for path-traversal patterns (../, ..%2f, %2e%2e/) against NPM paths — on any hit, trigger incident response and rotate credentials and configuration secrets.
      • Confirm that CVE-2024-55550 (the chaining partner) is also patched; combined, the two allow unauthenticated arbitrary file read, including configuration files and hashes.
      • Take an offline backup of MiCollab configuration, NPM mail stores and the associated database before applying the patch — data manipulation by the attacker is part of the impact profile.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: move MiCollab into a dedicated DMZ VLAN with explicit egress control; restrict outbound traffic to SMTP relays, SIP trunks and required Mitel backend services, default-deny everything else.
      • WAF/reverse-proxy rule: block HTTP requests targeting /npm-pwg/, /npm/ or other NPM endpoints when the path contains encoded or decoded traversal sequences (.., %2e%2e, ..%2f, ..%5c, double-encoded %252e). Enable normalisation before matching.
      • Enable IPS signatures for MiCollab/NPM path traversal (subscribe to Emerging Threats and vendor rule sets covering CVE-2024-41713 and CVE-2024-55550); SSL/TLS inspection in front of the server is required.
      • Webserver hardening: cap request-URI length, enable URL normalisation on the reverse proxy, remove direct internet routing to the MiCollab admin interface and gate admin access behind VPN plus MFA.
      • IAM and secret hygiene: after successful patching, rotate all local service accounts, LDAP bind credentials, SIP trunk secrets and API keys if there is any indication of prior compromise.
      • File-integrity monitoring on the MiCollab host (AIDE, Tripwire or EDR FIM) for /opt/mitel/, configuration directories and NPM data stores.

    3. Runbook step 3

      Detection rules

      • Webserver access logs (Apache/Tomcat in front of MiCollab): hunt for HTTP 200 responses on URIs containing .., %2e%2e, ..%2f or ..%5c under /npm. KQL shape: WebLogs | where url_path contains_any ("../","%2e%2e","..%2f") and url_path startswith "/npm".
      • Sigma shape for reverse proxy/WAF: detection.selection.cs-uri-stem|contains: ['/npm'] and cs-uri-query|re: '(\.\.|%2e%2e|%252e)' — severity high, exceptions only for documented scanners.
      • Zeek/Suricata: HTTP events whose uri matches the traversal regex against MiCollab server IPs; alert on more than five hits from a single source IP within 10 minutes (scanning behaviour).
      • Linux auditd on the MiCollab host: set -w /etc/ -p rwa and -w /opt/mitel/ -p wa, alert on file reads of sensitive paths by the Tomcat/MiCollab service user outside normal operational patterns.
      • EDR process ancestry: treat unusual child processes of the MiCollab/Java process (shell, curl, wget, nc, python) as high-severity alerts — path traversal is often followed by a second-stage action using harvested credentials.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NCSC NZ (CC BY 4.0), pwn.watch, CISA KEV Catalog, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    mitelmicollab
    • ≤ 9.8.1.201
    • —

    Vendors and products

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    NCSC NZActive exploitation affecting Mitel MiCollab (opens in a new tab)NCSC NZactively exploited
    NCSC NZDNU Active exploitation affecting Mitel MiCollab (opens in a new tab)NCSC NZactively exploited

    References & sources

    • mitel.comMitel advisory: Mitel MiCollabpwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-41713government-resource
    • pwn.watchpwn.watch: Mitel MiCollab: 2 exploited vulnerabilities (CVE-2024-41713, CVE-2024-55550)pwn-watch
    • NVD (NIST)NVD: CVE-2024-41713pwn-watch
    • NVD (NIST)NVD: CVE-2024-55550pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-41713
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-41713"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-41713.svg?lang=en" alt="CVE-2024-41713 – NEOSEC Intel" height="20"></a>