| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger a Stack Overflow vulnerability. A malicious actor may leverage this vulnerability to cause an application crash. |
| A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause an application crash, data corruption, or potentially execute arbitrary code in the context of the current process. |
| A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger an Out-of-Bounds Read (table-index lookup) vulnerability. A malicious actor may leverage this vulnerability to cause an application crash or potentially read sensitive data from the current process. |
| A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger an Out-of-Bounds Read (unvalidated element begin-pointer) vulnerability. A malicious actor may leverage this vulnerability to cause an application crash or potentially read sensitive data from the current process. |
| A maliciously crafted DWG file, when parsed through Autodesk AutoCAD or processed by the installed DWG thumbnail handler, can force an Out-of-Bounds Write vulnerability resulting in heap corruption. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DDS file, when parsed through Autodesk AutoCAD, can force a Heap-Based Buffer Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DWG file containing a malformed embedded image, when parsed through Autodesk AutoCAD, can force a Heap-Based Buffer Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DWF file, when parsed through Autodesk AutoCAD, can force a Heap-Based Buffer Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DGN file, when parsed through Autodesk AutoCAD, can force a Heap-Based Buffer Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DXF file, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Write vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted IES file, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Write vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DWG file containing an attacker-controlled Excel Data Link connection string, when processed through Autodesk AutoCAD, can cause AutoCAD to execute an attacker-controlled program. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current user. |
| A maliciously crafted DXF file, when parsed through Autodesk AutoCAD, can force a Type Confusion vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DXF file, when parsed through Autodesk AutoCAD, can force a Heap-Based Buffer Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process. |
| A maliciously crafted DWG file, when parsed by Autodesk AutoCAD, can trigger an Integer Overflow vulnerability in RLE bitmap decompression, resulting in an undersized heap allocation and subsequent heap buffer overflow. A malicious actor can leverage this vulnerability to cause a crash or potentially execute arbitrary code in the context of the current process. |
| A maliciously crafted DWG or DXF file containing a crafted field format string, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to read sensitive data from process memory. |
| A maliciously crafted DWG or DXF file containing an external reference with an attacker-controlled network path, when parsed through Autodesk AutoCAD, can force an Information Disclosure vulnerability. A malicious actor can leverage this vulnerability to disclose NTLM authentication information from the current user. |
| A maliciously crafted DXF file containing a scene-background object with an attacker-controlled network path, when parsed through Autodesk AutoCAD, can force an Information Disclosure vulnerability. A malicious actor can leverage this vulnerability to disclose NTLM authentication information from the current user. |
| A maliciously crafted DWG file containing an attacker-controlled network path, when parsed through Autodesk AutoCAD, can force an Information Disclosure vulnerability. A malicious actor can leverage this vulnerability to disclose NTLM authentication information from the current user. |
| A maliciously crafted DXF file containing crafted VBA project data, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to read sensitive data from process memory. |