Application crash via unchecked buffer copy
Published Jun 13, 2023 · Updated Nov 6, 2024
Buffer overflow in Zoom Meeting SDK before 5.13.0 allows local users with SDK authentication to crash an embedding application via crafted input. An undisclosed SDK buffer-copy path copies attacker-controlled input into a destination buffer without first checking that the input fits; Zoom has not named the function or input field. Reachability requires local access and authentication; successful triggering terminates the host process, which must be restarted.
Summary
What happened
Buffer overflow in Zoom Meeting SDK before 5.13.0 allows local users with SDK authentication to crash an embedding application via crafted input. An undisclosed SDK buffer-copy path copies attacker-controlled input into a destination buffer without first checking that the input fits; Zoom has not named the function or input field. Reachability requires local access and authentication; successful triggering terminates the host process, which must be restarted.
The record
- CVE
- CVE-2023-34115
- Published
- Jun 13, 2023
- Updated
- Nov 6, 2024
- Vendor
- Zoom Video Communications, Inc.
- Product
- Zoom Meeting SDK
- Classifications
- CWE-120, CAPEC-100, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 5.13.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo