CVE-2025-0150
Zoom Meeting Software Development Kit ≤ 6.3.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:HSummary
CVE-2025-0150 is a high-severity Incorrect Behavior Order (CWE-696) vulnerability in Zoom Meeting Software Development Kit. Its CVSS base score is 7.1 (High).
Operationally, ranked at the 38th 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 RA-5 (Vulnerability Monitoring and Scanning) — 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-0150 involves incorrect behavior order, classified under CWE-696, affecting Zoom Workplace Apps for iOS in versions before 6.3.0. This flaw enables an authenticated user to trigger a denial-of-service condition through network access. The vulnerability carries a CVSS v3.1 base score of 7.1, reflecting network attack vector (AV:N), low attack complexity (AC:L), low privileges required (PR:L), no user interaction (UI:N), unchanged scope (S:U), low confidentiality impact (C:L), no integrity impact (I:N), and high availability impact (A:H).
An authenticated user with low privileges can exploit this vulnerability remotely over the network, requiring minimal complexity and no user interaction on the target. Exploitation leads primarily to a denial-of-service, severely disrupting availability, alongside limited confidentiality exposure but without affecting integrity.
The Zoom security bulletin ZSB-25009, available at https://www.zoom.com/en/trust/security-bulletin/zsb-25009/, addresses this issue, with the vulnerability resolved in Zoom Workplace Apps for iOS version 6.3.0 and later.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7354
Vulnerability Data
Incorrect behavior order in some Zoom Workplace Apps for iOS before version 6.3.0 may allow an authenticated user to conduct a denial of service via network access.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages can discover incorrect ordering of related behaviors before deployment.
Vulnerability scanning may surface order-related weaknesses after code is built but does not address their root cause.
Mandating a documented development process and standards enforces review of behavior ordering within the software lifecycle.
Security and privacy engineering principles applied during design and implementation directly require correct sequencing of operations to avoid introducing order-dependent flaws.
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.
Secure SDLC practices directly enforce correct sequencing of security-relevant operations during design and coding.
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 ordering flaws but does not prevent them during development.
Secure development life cycle mandates correct sequencing of security activities, directly preventing incorrect behavior order.
Secure system architecture and engineering principles require proper ordering of design and implementation steps.
Secure coding standards enforce correct execution order of security-critical operations.
Change management may catch order-related issues during reviews but does not address root cause.