Hello Henry,
What version of windows agent are you running? this problem was detected and fixed in the following PR: https://github.com/wazuh/wazuh/pull/10259
So you should correctly get the cumulative patches belonging to the Microsoft Office 2016 package. So if it is not being obtained, it is expected that the vulnerability appears, since Vulnerability Detector works with the hotfixes it collects with Syscollector, but I tell you that in this case it should be fixed. Syscollector collects the list of hotfixes by regexing the Windows registries, so it’s always possible that we are not looking at some registry needed for a specific OS version (if it has been modified).
If the agent is not on the latest version at the time these vulnerability alerts appeared in the Office 2016 package, then this is normal, as the version in which the change of #10259 was added, was v4.3.0, as can be seen in the changelog: https://github.com/wazuh/wazuh/blob/master
Syscollector has been extended to collect missing Microsoft product hotfixes. (#10259)
So if you upgrade the agent to v4.3.4 and it re-syncs Syscollector with the manager, then the newly detected hotfixes should have been added, so the vulnerability should be mitigated.
Regards!
Hello Henry,
Let’s check what’s going on. To do so, I need more information from the agent.
Could you paste me the output of the following command executed on the agent side? The command would be /var/ossec/bin/wazuh-control info.
On the other hand, I would need more information from the affected agent to compare data and see if there is any problem.
I need the following information from the API:
To get the vulnerabilities, package, and hotfixes, you can get the information directly from the API, using the following queries:
(for example from the WUI you can use the following tool to run the queries: Modules -> tools -> Api console)
GET /vulnerability/{agent_id}
GET /syscollector/{agent_id}/packages
GET /syscollector/{agent_id}/hotfixes
Regards,
Juan Cabrera