CVE-2024-27239VulnerabilityPublished 25 Feb 2025Updated 1 Oct 2025

CVE-2024-27239: Zoom Workplace Apps and SDKs · Use After Free

Affects Zoom Workplace Apps and SDKsSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor for official patches or updates from Zoom Communications and apply them promptly once released to remediate the use-after-free vulnerability. 2. Restrict access to Zoom Workplace Apps and SDKs to only trusted and necessary authenticated users to reduce the attack surface. 3. Implement strong authentication mechanisms, including multi-factor authentication (MFA), to prevent unauthorized access that could lead to exploitation. 4. Employ network segmentation and firewall rules to limit exposure of Zoom Workplace services to internal networks or trusted endpoints only. 5. Monitor application logs and network traffic for unusual activity or repeated crashes that could indicate exploitation attempts. 6. Conduct regular security assessments and code reviews for any custom applications integrating Zoom SDKs to identify and mitigate memory management issues. 7. Prepare incident response plans specifically addressing denial of service scenarios affecting communication platforms to minimize downtime. 8. Educate users about the importance of credential security to prevent insider or credential-based attacks. These measures, combined with timely patching, will help mitigate the risk posed by this vulnerability beyond generic advice.

Description

Use after free in some Zoom Workplace Apps and SDKs may allow an authenticated user to conduct a denial of service via network access.

Impact

For European organizations, the impact of CVE-2024-27239 primarily concerns service availability of Zoom Workplace Apps and SDKs. Organizations relying on Zoom for internal collaboration, customer engagement, or SDK integrations in their workflows could experience disruptions if an attacker exploits this vulnerability to cause application crashes or denial of service. This could lead to operational downtime, reduced productivity, and potential reputational damage if critical communication channels are interrupted. Since the vulnerability requires authenticated access, insider threats or compromised user credentials could be leveraged to trigger the DoS. The impact is more pronounced in sectors with high dependence on real-time communication tools, such as finance, healthcare, government, and large enterprises. Additionally, organizations integrating Zoom SDKs into their own applications may face cascading effects if their custom solutions become unstable or unavailable. However, the lack of confidentiality or integrity impact reduces the risk of data breaches or manipulation through this vulnerability. Overall, the threat poses a moderate operational risk that must be addressed to maintain service continuity and trust in communication platforms.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zoom.com/en/trust/security-bulletin/zsb-24018/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Oct 2025, 10:47 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats