IrfanView 4.50 on 64-bit CADImage 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 classified as critical. This issue affects some unknown processing of the component CADImage plugin. The manipulation as part of dwg File leads to memory corruption. This vulnerability is referenced as CVE-2017-15767. The attack can only be performed from a local environment. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in IrfanView 4.50 on 64-bit (Image Processing Software) and classified as critical. This issue affects an unknown code block of the component CADImage 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 CADImage plugin version 12.0.0.5 allows attackers to execute arbitrary code or cause a denial of service via a crafted .dwg file, related to a "User Mode Write AV near NULL starting at CADIMAGE+0x00000000003d5b52."
The bug was discovered 10/21/2017. The weakness was published 10/22/2017 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-15767 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.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
Upgrading eliminates this vulnerability.
Similar entries are available at VDB-108367, VDB-108366, VDB-108364 and VDB-108363. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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/21/2017 🔍
10/22/2017 🔍
10/22/2017 🔍
10/23/2017 🔍
05/08/2026 🔍
Sources
Product: irfanview.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2017-15767 (🔍)
GCVE (CVE): GCVE-0-2017-15767
GCVE (VulDB): GCVE-100-108365
See also: 🔍
Entry
Created: 10/23/2017 10:11Updated: 05/08/2026 09:06
Changes: 10/23/2017 10:11 (63), 11/28/2019 19:56 (1), 05/08/2026 09:03 (1), 05/08/2026 09:06 (21)
Complete: 🔍
Committer: lywand
Cache ID: 216::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.