Camera and microphone access via library injection
Published Apr 1, 2020 · Updated Aug 4, 2024
Code injection in Zoom Client for Meetings 4.6.8 and earlier allows local users to access the camera and microphone without prompts. The macOS app carries the disable-library-validation entitlement, so dyld accepts a crafted proxy library from its bundle and runs that code inside Zoom's permission-bearing process. Exploitation requires a local foothold and yields device access only when Zoom already has camera or microphone permission.
Summary
What happened
Code injection in Zoom Client for Meetings 4.6.8 and earlier allows local users to access the camera and microphone without prompts. The macOS app carries the disable-library-validation entitlement, so dyld accepts a crafted proxy library from its bundle and runs that code inside Zoom's permission-bearing process. Exploitation requires a local foothold and yields device access only when Zoom already has camera or microphone permission.
The record
- CVE
- CVE-2020-11470
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1574.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Zoom dylib proxying demonstrationfunctional · demonstrated
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