Detection method for the latest Nessus Agent (x64)

[failau007]

The current detection method is looking for the version 10.2.1.20132, but the latest official Nessus Agent version is 10.2.1.20007. This is causing the Nessus Agent updates keep popping up in Software Center and the updates will fail.

[Spencer (Patch My PC)]

Hello and thank you for bringing this to our attention! We have checked and confirmed that Tenable released a newer version today (10.3.0) that should resolve this issue!

https://docs.tenable.com/releasenotes/Content/nessusagent/agent1030.htm

At this time, I would decline the current Nessus updates as to not cause further failures on pending clients. Once the new version has been added, run a Publisher sync and you should see the latest version being pulled in.

To keep tabs on catalog updates, you can visit our change log here: https://patchmypc.com/category/catalog-updates

[failau007]

I believe that the 10.3.0 version is still considered early access version which will probably not be added to PMPC nor our organization will opt in to. I just wanted to bring it to you guys' attention that the DisplayVersion in the Registry is still 10.2.1.20007 after installing the version 10.2.1.20132 that published by PMPC. Can you please clarify that the difference between version 10.2.1.20132 that published by PMPC on Nov 09 and the version 10.2.1.20007? I couldn't find any info about this on Tenable.

Thanks in advance.

[Spencer (Patch My PC)]

It looks like version 10.2.1.20007 was an out-of-band patch that resolved some found vulns (CVE-IDs: CVE-2022-3602; CVE-2022-3786) which is also using the same major version product code. Because both versions are using the same product code (10.2.1) it breaks our detection.

For reference, I have included the link to our release catalog showing the previous version with CVE's:
https://patchmypc.com/patch-my-pc-catalog-update-11-02-22

Here is the link showing the most current release (10.2.1.20132):
https://patchmypc.com/patch-my-pc-catalog-update-11-09-22

To remediate this, we will either be adding the latest version 10.3.0 (If it's Stable - Pending confirmation) or included a Pre-Req script that will properly identify the 10.2.1.20007 version.

Hopefully that helps answer your question! Unfortunately, I wasn't able to find anything regarding the previous update .20007 just links back to the overall 10.2.1 release notes.