Skip to content

Product

autodesk autocad vulnerabilities

198 published CVES affecting autodesk autocad, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
198
Critical
4
High
182
Medium
8
Low
4
Unscored
0
CISA KEV
0

Latest autodesk autocad CVEs

Newest publication first · page 1 of 8

  1. HighCVSS 7.8 EPSS 0.18%

    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...

  2. HighCVSS 7.8 EPSS 0.16%

    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 arb...

  3. MediumCVSS 5.5 EPSS 0.16%

    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.

  4. MediumCVSS 5.5 EPSS 0.16%

    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.

  5. HighCVSS 7.8 EPSS 0.17%

    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 cur...

  6. HighCVSS 7.8 EPSS 0.16%

    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.

  7. HighCVSS 7.8 EPSS 0.17%

    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.

  8. LowCVSS 3.3 EPSS 0.16%

    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 u...

  9. HighCVSS 7.8 EPSS 0.17%

    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...

  10. HighCVSS 7.8 EPSS 0.17%

    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.

  11. HighCVSS 7.8 EPSS 0.28%

    A maliciously crafted DXF file, when parsed through Autodesk AutoCAD, can force a Heap-Based Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

  12. HighCVSS 7.8 EPSS 0.28%

    A maliciously crafted MODEL file, when parsed through certain Autodesk products, can force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, or execute arbitrary code in the context of the current proc...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.