DWG TrueView version and updates

DWG TrueView version and updates

gordow
Advocate Advocate
2,054 Views
2 Replies
Message 1 of 3

DWG TrueView version and updates

gordow
Advocate
Advocate

Our ISO recently notified us that one of our computers is running a version of DWG TrueView 2023 that has a vulnerability and will be quarantined if not updated.  Here is the notice:

 

ISSUE: Vuln: Autodesk DWG TrueView 2023 < 2023.1.1 RCE

 

The remote host has an install of Autodesk DWG TrueView version 2023 prior to 2023.1.1. It is, therefore, affected by a remote code execution vulnerability due to DLL search order hijacking.

 

So, the version on the computer needs to be updated.  I cannot figure out how to determine the current version.  On the computer I use, when I run DWG TrueView 2023 and look at "About...", it says the product version is T.72.0.0, see attached screen grab, which doesn't align with the format 2023.1.1.  How can I determine if the version of DWG TrueView running is version 2023.1.1 or newer? 

 

Also, when I look at the products update page, I don't see DWG TrueView listed.  Is it updated when other applications are updated?  Can DWG TrueView be updated by itself? 

 

Any help or insight will be appreciated.  Thanks.

 

Gordow

0 Likes
Accepted solutions (1)
2,055 Views
2 Replies
Replies (2)
Message 2 of 3

andrewiv
Mentor
Mentor

If you go to the control panel, programs and features, and find DWG Trueview it should show what version you have installed there.

andrewiv_0-1746634680049.png

 

Andrew In’t Veld
Designer / CAD Administrator

0 Likes
Message 3 of 3

gordow
Advocate
Advocate
Accepted solution

DWG TrueView didn't show up in Programs and Features until I ran the installer to update and got to T.212.0.0.  There, it showed the version as 24.2.212.0, which still doesn't tell me it I got to 2023.1.1 or newer.  However, a link in the original ISO email (https://www.tenable.com/plugins/nessus/169504) took me to a webpage, attached, outlining the vulnerability.  On the page, it states that 2023.1.1 (build 24.2.153.0) or newer is required to solve the issue.  Since I am now at 24.2.212.0, I believe the issue is resolved. 

 

Andrew, your suggestion, while a way to determine the version running, didn't answer the question of whether I was actually running a version 2023.1.1 or newer.  I can't mark your input as the Accepted Solution, but thank you for reading may post and offering your input.  It took further investigation to find a page that actually stated what build 2023.1.1 was. 

 

IMO, this kind of information should be easier to find. 

 

gordow

0 Likes