Cyber Resilience

CVE-2024-45419

Zoom Meeting Software Development Kit ≤ 6.2.0

Published
19 November 2024
Modified
19 August 2025
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0051 41th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2024-45419 is a high-severity Unchecked Return Value (CWE-252) vulnerability in Zoom Meeting Software Development Kit. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 41th 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.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper input validation in some Zoom Apps may allow an unauthenticated user to conduct a disclosure of information via network access.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-45421Same product: Zoom Meeting Software Development Kit
CVE-2025-0151Same product: Zoom Meeting Software Development Kit
CVE-2025-30668Same product: Zoom Meeting Software Development Kit
CVE-2025-27440Same product: Zoom Meeting Software Development Kit
CVE-2025-27439Same product: Zoom Meeting Software Development Kit
CVE-2025-0144Same product: Zoom Meeting Software Development Kit
CVE-2024-42436Same product: Zoom Meeting Software Development Kit
CVE-2024-42438Same product: Zoom Meeting Software Development Kit
CVE-2024-42437Same product: Zoom Meeting Software Development Kit
CVE-2024-27246Same product: Zoom Meeting Software Development Kit

Affected Assets

zoom
meeting software development kit
≤ 6.2.0 · ≤ 6.2.0 · ≤ 6.2.0
zoom
rooms
≤ 6.2.0 · ≤ 6.2.0 · ≤ 6.2.0
zoom
rooms controller
≤ 6.2.0 · ≤ 6.2.0 · ≤ 6.2.0
zoom
video software development kit
≤ 6.2.0 · ≤ 6.2.0 · ≤ 6.2.0
zoom
workplace
≤ 6.2.0 · ≤ 6.2.0
zoom
workplace desktop
≤ 6.2.0 · ≤ 6.2.0 · ≤ 6.2.0
zoom
workplace virtual desktop infrastructure
≤ 6.0.14 · 6.0.15 — 6.1.12

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and code evaluation can discover instances where return values are ignored.

Requiring a documented development process and coding standards can mandate explicit checking of all function return values.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require checking and handling all function return values to detect error conditions.

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.

finds

Security testing in development and acceptance can detect missing return-value checks.

prevents

Secure development life cycle mandates verification of return values to prevent undetected failures.

prevents

Application security requirements include input/output validation and error handling that covers return-value checks.

degrades

Secure system architecture and engineering principles require robust error handling and defensive coding practices.

prevents

Secure coding explicitly requires checking return values to avoid CWE-252.

References