dbcve.org
Advance SteelApplication · Autodesk

CVE-2019-7361

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 attacker may convince a victim to open a malicious action micro (.actm) file that has serialized data, which may trigger a code execution 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.

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 · high confidence

A deserialization vulnerability in Autodesk Advance Steel 2018 and various AutoCAD 2018 products allows remote code execution when victims open specially crafted .actm (action macro) files containing malicious serialized data. The attacker must trick the victim into opening the malicious file, making it a user-interaction-dependent vector.

MitigationUsers should not open untrusted .actm files from unknown sources; organizations should implement email/file filters to block suspicious .actm attachments and ensure all affected Autodesk 2018 products are patched with the vendor updates.

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*' -or $_.DisplayName -like '*AutoCAD*' -or $_.DisplayName -like '*Advance Steel*'}
    Affected if Any 2018 version of Autodesk Advance Steel, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or AutoCAD MEP is listed as installed
  2. Verify exact version matches 2018
    For each identified product, right-click in Programs and Features and view the Version column, or query the specific product's version via registry at HKLM\SOFTWARE\Autodesk\<ProductName>\<Version>
    Affected if The installed version is exactly 2018 (or falls within a 2018.x release line if the vendor clarifies the range)
  3. Confirm .actm file handler is registered
    Open Command Prompt and run: assoc .actm OR reg query HKCR\.actm to see if .actm extension is associated with an AutoCAD action macro handler
    Affected if The .actm extension is associated with an Autodesk application, meaning the software can open these files
  4. Check if .actm files have been opened recently
    Open Event Viewer > Windows Logs > Application and filter by source 'AutoCAD' or 'AcAuthLisp' around the time of suspected incident, or check browser/download histories for .actm file downloads
    Affected if Any .actm files from untrusted sources were opened or exist on the system

If any Autodesk 2018 product is installed and the system can open or has opened .actm files, the environment is potentially affected by this deserialization vulnerability.

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

Users should not open untrusted .actm files from unknown sources; organizations should implement email/file filters to block suspicious .actm attachments and ensure all affected Autodesk 2018 products are patched with the vendor updates.

Fix this in Advance Steel Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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