IrfanView 4.50 on 64-bit BabaCAD4Image Plugin dwg File memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IrfanView 4.50 on 64-bit. It has been rated as critical. This vulnerability affects unknown code of the component BabaCAD4Image Plugin. The manipulation as part of dwg File leads to memory corruption. This vulnerability is listed as CVE-2017-15755. The attack must be carried out locally. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, has been found in IrfanView 4.50 on 64-bit (Image Processing Software). This issue affects an unknown function of the component BabaCAD4Image Plugin. The manipulation as part of a dwg File leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
IrfanView 4.50 - 64bit with BabaCAD4Image plugin version 1.3 allows attackers to cause a denial of service or possibly have unspecified other impact via a crafted .dwg file, related to "Data from Faulting Address controls Branch Selection starting at verifier!AVrfpDphFindBusyMemoryNoCheck+0x0000000000000091."
The bug was discovered 10/22/2017. The weakness was presented 10/22/2017 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-15755 since 10/21/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
See VDB-108357, VDB-108356, VDB-108355 and VDB-108354 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://www.irfanview.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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 |
OpenVAS ID: 802576
OpenVAS Name: IrfanView Multiple DoS Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
10/21/2017 🔍10/22/2017 🔍
10/22/2017 🔍
10/22/2017 🔍
10/23/2017 🔍
05/06/2026 🔍
Sources
Product: irfanview.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2017-15755 (🔍)
GCVE (CVE): GCVE-0-2017-15755
GCVE (VulDB): GCVE-100-108353
See also: 🔍
Entry
Created: 10/23/2017 09:16Updated: 05/06/2026 17:23
Changes: 10/23/2017 09:16 (63), 11/28/2019 17:31 (1), 05/06/2026 17:20 (1), 05/06/2026 17:23 (21)
Complete: 🔍
Committer: lywand
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.