Advance SteelApplication · Autodesk

CVE-2019-7358

HIGH · 7.8 CVSS v3.0 Published 2019-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An exploitable heap overflow vulnerability in the DXF-parsing functionality in Autodesk Advance Steel 2018, Autodesk AutoCAD 2018, Autodesk AutoCAD Architecture 2018, Autodesk AutoCAD Electrical 2018, Autodesk AutoCAD Map 3D 2018, Autodesk AutoCAD Mechanical 2018, Autodesk AutoCAD MEP 2018, Autodesk AutoCAD P&ID 2018, Autodesk AutoCAD Plant 3D 2018, Autodesk AutoCAD LT 2018, and Autodesk Civil 3D 2018. A specially crafted DXF file may cause a heap overflow, resulting in code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap overflow vulnerability in Autodesk products' DXF file parsing functionality. Specially crafted malicious DXF files can trigger heap buffer overflow during parsing, potentially allowing remote code execution in the context of the application process.

MitigationAvoid opening DXF files from untrusted sources; apply vendor patches from Autodesk when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advance SteelApplication
Affected:= 2018
AutocadApplication
Affected:= 2018
Autocad ArchitectureApplication
Affected:= 2018
Autocad ElectricalApplication
Affected:= 2018
Autocad LtApplication
Affected:= 2018
Autocad Map 3dApplication
Affected:= 2018
Autocad MechanicalApplication
Affected:= 2018
Autocad MepApplication
Affected:= 2018

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Autodesk products
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Autodesk*'}
    Affected if Any Autodesk product from the affected list is present (Advance Steel, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or AutoCAD MEP)
  2. Verify product version
    In the Programs and Features list, check the Version column for the identified product, or right-click the product executable (typically in C:\Program Files\Autodesk\) and view Properties > Details > File Version
    Affected if The version is exactly 2018
  3. Confirm DXF file handling capability
    Check if the product can open or import DXF files by attempting to open a .dxf file or inspecting file associations in the application's options/preferences under File Formats
    Affected if DXF file handling is enabled (default state for AutoCAD products)
  4. Determine exposure to untrusted DXF files
    Review workflow for DXF file handling: check if users commonly open DXF files from external/untrusted sources, or inspect recent DXF file access logs if available
    Affected if Users or automated processes open DXF files from untrusted or external sources

Your environment is affected if you have any Autodesk product from the affected list installed at version 2018 and that product handles DXF files, which is the default behavior.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening DXF files from untrusted sources; apply vendor patches from Autodesk when available.

Fix this in Advance Steel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7358 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data