OpenCV 3.4.1 loadsave.cpp validateInputImageSize code ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenCV 3.4.1. This impacts the function validateInputImageSize of the file modules/imgcodecs/src/loadsave.cpp. The manipulation leads to denial of service.
This vulnerability is documented as CVE-2018-7712. The attack can be initiated remotely. There is not any exploit available.
The actual existence of this vulnerability is currently in question.
Details
A vulnerability was found in OpenCV 3.4.1 (Image Processing Software). It has been rated as problematic. This issue affects the function validateInputImageSize of the file modules/imgcodecs/src/loadsave.cpp. The manipulation with an unknown input leads to a code vulnerability. Using CWE to declare the problem leads to CWE-17. Impacted is availability. The summary by CVE is:
The validateInputImageSize function in modules/imgcodecs/src/loadsave.cpp in OpenCV 3.4.1 allows remote attackers to cause a denial of service (assertion failure) because (size.height <= (1<<20)) may be false.
The bug was discovered 03/05/2018. The weakness was released 03/05/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-7712 since 03/05/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 253213 (Linux Distros Unpatched Vulnerability : CVE-2018-7712), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (253213). Entries connected to this vulnerability are available at VDB-114102 and VDB-114103. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.5
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: CodeCWE: CWE-17
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 253213
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2018-7712
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/05/2018 🔍03/05/2018 🔍
03/05/2018 🔍
03/05/2018 🔍
03/06/2018 🔍
08/24/2025 🔍
Sources
Advisory: 10998Status: Not defined
Disputed: 🔍
CVE: CVE-2018-7712 (🔍)
GCVE (CVE): GCVE-0-2018-7712
GCVE (VulDB): GCVE-100-114101
See also: 🔍
Entry
Created: 03/06/2018 07:51Updated: 08/24/2025 21:46
Changes: 03/06/2018 07:51 (57), 01/10/2020 16:12 (1), 02/17/2023 07:21 (3), 07/23/2024 23:18 (28), 08/24/2025 21:46 (3)
Complete: 🔍
Cache ID: 216:FEA:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.