This is a very interesting case indeed.

While VulnDetect has the capability of detecting libraries, then this is beyond the current scope of VulnDetect.

However, due to the fact that this is being actively exploited and I can see that there is a LOT of software, including Avira AntiVir, WinRAR, XnView, PeaZip, Bandizip, SpeedCommander, and tonnes of software I never heard about, that utilizes it and sounds like it could provide attack vectors, I will add it for now.

But do not expect us to support libraries in general, anytime soon.

Later in the week, when the second iteration of our bundling is going live, then I will let the security state of unacev2.dll affect the state of the parent program.

@KI108 Thank you for providing this information.
Now @Tom has all information to add this application.

@KI108 Thank you for providing this information.
Now @Tom has all information to add this application.

@KI108 Thank you for providing this information.
Now @Tom has all information to add this application.

@Tom OK, there is a new version

File name and path: C:\Ruby26\bin\ruby.exe Product Name: Ruby interpreter 2.6.1p33 [i386-mingw32] Internal Name: ruby.exe Original Filename: ruby.exe File Description: Ruby interpreter (CUI) 2.6.1p33 [i386-mingw32] Company: http://www.ruby-lang.org/ Legal Copyright: Copyright (C) 1993-2019 Yukihiro Matsumoto Legal Trademarks: Comments: 2019-01-30 File Version String: 2.6.1p33 File Version: 2.6.1.33 Product Version String: 2.6.1p33 Product Version: 2.6.1.33

C:>ruby -v
ruby 2.6.1p33 (2019-01-30 revision 66950) [i386-mingw32]

Detection added. However, I did not find a good way to retrieve information beyond the 0.3 or 0.3.0.0. And all users had the same version, so we have to assess if there is a better way of detecting this as new versions are released.

@Anselm Thank you

We are working on this, but we want to see if we can utilize the Rules for JRE in a smart way, so we don't have to duplicate it.