ImageWorsener 1.3.0 imagew-miff.c iwmiffr_convert_row32 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in ImageWorsener 1.3.0. Affected by this issue is the function iwmiffr_convert_row32 of the file imagew-miff.c. Executing a manipulation can lead to memory corruption.
This vulnerability is tracked as CVE-2017-7623. The attack is restricted to local execution. No exploit exists.
Details
A vulnerability has been found in ImageWorsener 1.3.0 (Image Processing Software) and classified as problematic. This vulnerability affects the function iwmiffr_convert_row32 of the file imagew-miff.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. CVE summarizes:
The iwmiffr_convert_row32 function in imagew-miff.c in libimageworsener.a in ImageWorsener 1.3.0 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted file.
The bug was discovered 04/03/2017. The weakness was disclosed 04/10/2017 (GitHub Repository). The advisory is available at github.com. This vulnerability was named CVE-2017-7623 since 04/10/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $0-$5k.
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 SecurityFocus (BID 97577†). The entry VDB-99563 is pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD 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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/03/2017 🔍04/05/2017 🔍
04/10/2017 🔍
04/10/2017 🔍
04/10/2017 🔍
04/11/2017 🔍
11/28/2022 🔍
Sources
Advisory: 12Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-7623 (🔍)
GCVE (CVE): GCVE-0-2017-7623
GCVE (VulDB): GCVE-100-99562
SecurityFocus: 97577 - ImageWorsener 'src/imagew-miff.c' Remote Heap Buffer Overflow Vulnerability
OSVDB: - CVE-2017-7623 - ImageWorsener - Buffer Over-Read Issue
See also: 🔍
Entry
Created: 04/11/2017 09:48Updated: 11/28/2022 09:17
Changes: 04/11/2017 09:48 (64), 08/28/2020 12:43 (1), 11/28/2022 09:17 (4)
Complete: 🔍
Cache ID: 216:CD8:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.