Memory corruption via untrusted audio packet length
Published Jan 28, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in Accfly Wireless Security IR Camera System 720P 3.10.73 through 4.15.77 allows remote attackers to corrupt heap memory. CNetClientTalk::OprMsg copies incoming audio data with memcpy using a sender-controlled packet-header length rather than the destination size. The proprietary network protocol requires no authentication, but the continuously changing heap makes controlled code execution unreliable.
Summary
What happened
Heap-based buffer overflow in Accfly Wireless Security IR Camera System 720P 3.10.73 through 4.15.77 allows remote attackers to corrupt heap memory. CNetClientTalk::OprMsg copies incoming audio data with memcpy using a sender-controlled packet-header length rather than the destination size. The proprietary network protocol requires no authentication, but the continuously changing heap makes controlled code execution unreliable.
The record
- CVE
- CVE-2020-25783
- Published
- Jan 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2021CVE 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.
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