Code execution via malformed recording file parsing
Published Jun 4, 2021 · Updated Nov 7, 2024
Memory corruption in Cisco Webex recording players before 41.2 allows attackers to execute code through a malicious ARF or WRF file. The players insufficiently validate values while parsing ARF and WRF recordings, allowing crafted fields to corrupt memory during playback. Exploitation requires a targeted user to open the file locally, and resulting code runs with that user's privileges.
Summary
What happened
Memory corruption in Cisco Webex recording players before 41.2 allows attackers to execute code through a malicious ARF or WRF file. The players insufficiently validate values while parsing ARF and WRF recordings, allowing crafted fields to corrupt memory during playback. Exploitation requires a targeted user to open the file locally, and resulting code runs with that user's privileges.
The record
- CVE
- CVE-2021-1503
- Published
- Jun 4, 2021
- Updated
- Nov 7, 2024
- Vendor
- ClamAV
- Product
- Webex Meetings
- Classifications
- CWE-119, CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2021CVE publishedPublication date reported by the CVE source.
- Nov 7, 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=n/a
What conditions does exploitation require?
What is affected?
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