SecTeer VulnDetect Support Forum

    VulnDetect

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Download VulnDetect Installer

    [Solved] FreeCommander XE - Wrong Version detected after Update to 2019 release 790 Donor

    Solved Detection Issues
    2
    6
    1774
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • OLLI_S
      OLLI_S Community Moderator last edited by OLLI_S

      Today I installed an update for FreeCommander XE (new version 2019 release 790 donor) but VulnDetect does not detect the installed version (version 2019 release 790 public is shown)!
      So you detect public although I have donor installed.
      In the Configuration of VulnDetect I see: Last Inspection 35 minutes ago.


      Here the information extracted from the EXE file:

      File name and path:     C:\Program Files\FreeCommander XE\FreeCommander.exe
      Product Name:           FreeCommander XE
      Internal Name:          
      Original Filename:      
      
      File Description:       FreeCommander (x64) - file manager for Windows
      Company:                Marek Jasinski
      Legal Copyright:        www.freecommander.com
      Legal Trademarks:       
      Comments:               
      
      File Version String:    2019.0.0.790
      File Version:           2019.0.0.790
      Product Version String: 2019.0.0.790
      Product Version:        2019.0.0.790
      
      1 Reply Last reply Reply Quote 0
      • OLLI_S
        OLLI_S Community Moderator last edited by

        @Tom said in FreeCommander XE - Wrong Version detected after Update to 2019 release 790 Donor:

        a 64bit executable is assumed to be Donor

        This is the correct way.
        So I mark the issue as solved.

        1 Reply Last reply Reply Quote 0
        • T
          Tom VulnDetect Team Member @OLLI_S last edited by

          @OLLI_S There is no useful information in the Uninstall in the registry.
          So we will continue to detect in the usual manner, except, a 64bit executable is assumed to be Donor and the 64bit will now bundle the 32bit.

          /Tom
          Download the latest SecTeer VulnDetect agent here:
          https://vulndetect.com/dl/secteerSetup.exe

          1 Reply Last reply Reply Quote 0
          • OLLI_S
            OLLI_S Community Moderator last edited by

            @Tom How are you going to fix this issue?
            Are you waiting for the Registry detection?

            T 1 Reply Last reply Reply Quote 0
            • OLLI_S
              OLLI_S Community Moderator last edited by

              If you can detect x64 then you have the difference.
              On the official download page: https://freecommander.com/en/downloads/
              It says: FreeCommander XE 64-bit is currently available as bonus for the donors.

              1 Reply Last reply Reply Quote 0
              • T
                Tom VulnDetect Team Member last edited by

                See my response here:
                https://vulndetect.org/topic/552/freecommander-version-number

                I'm afraid we can't do much, unless you can suggest an alternative way of detecting the difference.

                /Tom
                Download the latest SecTeer VulnDetect agent here:
                https://vulndetect.com/dl/secteerSetup.exe

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Download SecTeer Personal VulnDetect - an alternative to the long lost Secunia PSI

                Please see our Privacy and Data Processing Policy
                Sponsored and operated by SecTeer | VulnDetect is a replacement for the EoL Secunia PSI
                Forum software by NodeBB