ImageWorsener 1.3.1 imagew-util.c iw_get_ui16le memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ImageWorsener 1.3.1. It has been classified as problematic. This impacts the function iw_get_ui16le of the file imagew-util.c. Performing a manipulation results in memory corruption.
This vulnerability is known as CVE-2017-9206. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in ImageWorsener 1.3.1 (Image Processing Software). It has been classified as problematic. This affects the function iw_get_ui16le of the file imagew-util.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
The iw_get_ui16le function in imagew-util.c:405:23 in libimageworsener.a in ImageWorsener 1.3.1 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted image, related to imagew-jpeg.c.
The bug was discovered 05/20/2017. The weakness was published 05/23/2017 (Website). It is possible to read the advisory at blogs.gentoo.org. This vulnerability is uniquely identified as CVE-2017-9206 since 05/22/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 3 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.
Similar entries are available at VDB-101710, VDB-101711, VDB-101712 and VDB-101713. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
05/20/2017 🔍05/22/2017 🔍
05/23/2017 🔍
05/23/2017 🔍
05/23/2017 🔍
12/07/2022 🔍
Sources
Advisory: b45cb1b665a14b0175b9cb1502ef7168e1fe0d5dStatus: Not defined
CVE: CVE-2017-9206 (🔍)
GCVE (CVE): GCVE-0-2017-9206
GCVE (VulDB): GCVE-100-101715
OSVDB: - CVE-2017-9206 - Imageworsener Project - Imageworsener - Medium
See also: 🔍
Entry
Created: 05/23/2017 13:06Updated: 12/07/2022 09:07
Changes: 05/23/2017 13:06 (58), 10/02/2020 16:20 (2), 12/07/2022 09:07 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.