CVE-2025-62484
Zoom Meeting Software Development Kit ≤ 6.5.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NSummary
CVE-2025-62484 is a high-severity Inefficient Regular Expression Complexity (CWE-1333) vulnerability in Zoom Meeting Software Development Kit. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — 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.
CVE-2025-62484 is a high-severity vulnerability stemming from inefficient regular expression complexity (CWE-1333) in certain Zoom Workplace Clients prior to version 6.5.10. This flaw affects the client software, enabling potential exploitation through crafted network input that triggers excessive computation during regex processing, commonly known as a ReDoS (Regular Expression Denial of Service) condition adapted for privilege escalation.
An unauthenticated attacker (PR:N) with network access (AV:N) can exploit this vulnerability with low complexity (AC:L), though it requires user interaction (UI:R), such as a user clicking a malicious link or accepting a connection in a Zoom session. Successful exploitation leads to escalation of privilege, granting high confidentiality (C:H) and integrity (I:H) impacts without affecting availability (A:N) or changing scope (S:U), as scored at CVSS 8.1 (CVSS:3.1). The attacker could potentially manipulate client privileges to access sensitive data or alter application behavior.
Zoom's security bulletin (ZSB-25048) advises updating affected Zoom Workplace Clients to version 6.5.10 or later as the primary mitigation, addressing the regex inefficiency to prevent exploitation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-175318
Vulnerability Data
Inefficient regular expression complexity in certain Zoom Workplace Clients before version 6.5.10 may allow an unauthenticated user to conduct an escalation of privilege via network access.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover inefficient regex patterns via performance or static analysis.
Development standards and tools can require safe regex construction and forbid known exponential patterns.
Denial-of-service protections limit resource exhaustion caused by expensive regex evaluation.
Input validation can constrain data that would otherwise trigger worst-case regex complexity.
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.
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 can detect and reject regex patterns with exponential worst-case complexity.
Secure development lifecycle mandates review of algorithmic efficiency, directly addressing ReDoS-prone regex.
Application security requirements can specify input-validation rules that limit regex complexity.
Secure architecture principles encourage avoidance of computationally expensive constructs such as catastrophic backtracking.
Secure coding standards explicitly prohibit or limit the use of inefficient regular expressions.