Code execution via unchecked JSON string length
Published Jan 3, 2020 · Updated Aug 4, 2024
Out-of-bounds write in OpenCV 4.1.0 allows remote attackers to execute code via a crafted JSON file supplied to an application. The JSONParser in modules/core/src/persistence_json.cpp appends decoded string data with memcpy into a fixed-size buffer without checking cumulative length, causing heap corruption. Exploitation requires an application to load attacker-controlled JSON; corruption can crash the process or enable code execution.
Summary
What happened
Out-of-bounds write in OpenCV 4.1.0 allows remote attackers to execute code via a crafted JSON file supplied to an application. The JSONParser in modules/core/src/persistence_json.cpp appends decoded string data with memcpy into a fixed-size buffer without checking cumulative length, causing heap corruption. Exploitation requires an application to load attacker-controlled JSON; corruption can crash the process or enable code execution.
The record
- CVE
- CVE-2019-5064
- Published
- Jan 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- OpenCV
- Product
- OpenCV
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=OpenCV 4.1.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.
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