CVE-2024-41710
A vulnerability in the Mitel 6800 Series, 6900 Series, and 6900w Series SIP Phones, including the 6970 Conference Unit, through R6.4.0.HF1 (R6.4.0.136) could allow an authenticated attacker with administrative privilege to conduct an argument injection attack, due to insufficient parameter sanitization during the boot process. A successful exploit could allow an attacker to execute arbitrary commands within the context of the system.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-41710 being exploited?
Yes. CVE-2024-41710 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-41710?
CVE-2024-41710 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-41710?
Yes. A fix has been recorded for CVE-2024-41710. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-41710 affect?
CVE-2024-41710 affects mitel:6970_firmware, mitel:6940w_sip_firmware, mitel:6930w_sip_firmware, mitel:6920w_sip_firmware, and 11 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 13 Feb 2025 (SSVC 2.0.3).
timeline
- 12 Aug 2024Published
- 12 Feb 2025Added to CISA KEV (exploited in the wild) · 183 days (about 6 months) later
- 13 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 5 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 231 days (about 8 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkmitel.com /support/security-advisories
- Linkgithub.com /kwburns/CVE/blob/main/Mitel/6.3.0.1020/README.md
- Linkmitel.com /support/security-advisories/mitel-product-security-advisory-24-0019
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-41710
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.