Posts made by VulnDetect

The reason you saw this in the past, is that you used to use the Personal edition.

The Personal edition by default displays files that are considered libraries.

The issue with 7z.exe is that it is hugely popular, as a library. In fact, there is an average of 1.6 7z.exe files on each host that uses VulnDetect, which are "real" libraries, only a tiny fraction of these are portable, like yours.

22% of all hosts have a "real" 7-Zip installation. These "real" installations are displayed correctly and updated automatically.

Sadly, there is no simple way (for us) to make a distinction between a 7z.exe that is used as a library, and one that is a portable file, like yours.

The Privacy Policy has been updated to reflect that data now is stored at Hetzner, rather than at AWS.

The module that allows custom content like the Privacy Policy has also been reinstalled and reactivated.

Ping @tom if there are any issues with the forum.

The forum is now updated and hosted at Hetzner, like all other production systems.

We are currently updating the forum, changing hosting and moving the database.

The systems are all back online.

The maintenance, which really wasn't maintenance at all, but rather a move of all our infrastructure from AWS in Ireland, to Hetzner in Germany.

The policies will be updated soon, to reflect this. There is still some backup data at AWS, which will be purged soon.

Also, we will continue to use AWS S3 for some transient storage.

All databases and all processing of data is now conducted on our "own" systems hosted at Hetzner.

This has given us significant more computing resources as well as cost savings.

More importantly, we have upgraded the setup, in almost every way possible, allowing much smoother deployment of changes, as well as much more control and insight of operations.

The coming week or two, will likely call for some fine tuning and tweaking, but all in all, it looks like everything is running smoothly.

We are currently conducting system maintenance. This means that we will be closing all access to the services.

The UI is expected to be back within an hour.

The Agent servers and processing of inspections are expected to be back online within 3 hours.

The maintenance will not affect the forum, only services on *.vulndetect.com are affected.

We will update this post or post new comments when there is new information.

@olli_s Thank you, it was added some days ago, but some changes were made to last few versions, so the detection had to be updated.

That is now in place and so is the icon, thank you.

Thank you for bringing this to our attention. It appears that there is at least three different "names", and this appears to be based on the license.

We have changed the rules, so we now select a title based on what is in "Add/Remove".

@olli_s Fixed!

@olli_s Added, thank you

@olli_s Added, thank you

@OLLI_S Added

@olli_s Interesting, thank you
We have updated the product to take beta versions into account.

@gregalexandre Ouch...
Thank you for pointing this out again.
Guess I have to make the instructions for this product more clear

@olli_s But OLLI....

Did you not notice the Internal?

This detection was not yet released to all users

But thank you, I reviewed the product now and corrected it.

The detection is no longer Internal.

@olli_s Thank you, icon added

@gregalexandre Is this from your primary machine? (I checked your result in the backend).

On, what I presume is, your primary machine, it is displayed correctly.

And from all I can tell, that particular release of Office has been displayed correctly since 2nd March (it was released on 1st March).

If this is not from your primary machine, then please send me the username for the other machine in a chat message and I will review the result manually.

We will review and add these requests.

Generally speaking, we will prioritize the efforts based on the number of installations.

Currently, we can only support software which have installers that support silent install parameters, which preserve user settings, and which allows system wide installation.

This means that software which only supports "per user" installations or where the vendor intentionally prevented the installer from doing updates, such as Microsoft Teams, isn't supported.

Earlier today the installer for 3.0.12 was released, and short time ago the security page was updated. However, the actual VideoLAN advisory, is still 404.

Anyway, the rule is updated and a package is available, and the first users and customers has applied the updated version.

Again, thank you for reporting this.

@GregAlexandre Thank you.

It appears that they do have a fix in the pipeline:
https://code.videolan.org/videolan/vlc-3.0/-/commit/ec1f55ee9ace5cc675395a1bc9700d99679e7e8c

For some reason they haven't released 3.0.12 yet.

We have flagged 3.0.11 as Insecure and will closely monitor the release of 3.0.12.