CVE-2025-30662
Zoom Workplace Virtual Desktop Infrastructure ≤ 6.3.14
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:NSummary
CVE-2025-30662 is a medium-severity Reliance on File Name or Extension of Externally-Supplied File (CWE-646) vulnerability in Zoom Workplace Virtual Desktop Infrastructure. Its CVSS base score is 6.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Double File Extension (T1036.007); ranked at the 3th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-175306
Vulnerability Data
Symlink following in the installer for the Zoom Workplace VDI Plugin macOS Universal installer before version 6.3.14, 6.4.14, and 6.5.10 in their respective tracks may allow an authenticated user to conduct a disclosure of information 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
Requires validation of information inputs, which structurally stops reliance on untrusted file names or extensions by forcing content-based checks.
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 require content-based validation instead of trusting file extensions for externally supplied files.
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 the weakness, but the control does not guarantee its elimination.
Restricting software installation can limit dangerous file types but does not enforce content-based validation.
Web filtering can block risky file extensions but does not address server-side file handling logic.
Secure SDLC requires proper file-type validation, directly mitigating reliance on untrusted names or extensions.
Application security requirements can mandate content inspection, but the control itself does not prescribe the technique.
Secure architecture principles encourage safe file handling, yet the control is broader than this specific weakness.