Hi
We've encountered a peculiar issue with vulnerability detection / scanning of above CVE. After throrough investigation of the issue we have not been able to identify why Wazuh reports a system to be affected by the CVE.
Our review showed that there's maven related RHSA (4797 and 4798) that deal with the issue in relation to different maven versions 3.6 and 3.5 respectively.
Initially we thoughed that the issue was with RHEL security paching, but after several rounds of monhtly pacthing and manual 'dnf' / 'yum' checks on reported systems having the CVE active, we deemed that not to be the case. Repository manager does not give any updates for the CVE, hence we cannot do anything for the issue.
One of the challenges in this case is that the maven is bundled with apache packages and not separately installed by the package manager on the servers. Which obviously makes it that much harder to identify.
All the affected servers are running RHEL 8.7 and the particular packages that are reported vulnerable by Wazuh are
Package less than 1.4-7.module+el8.6.0+13337+afcb49ec
Package less than 1.13-3.module+el8.6.0+13337+afcb49ec
Package less than 1:2.6-6.module+el8.6.0+13337+afcb49ec
Package less than 3.9-4.module+el8.6.0+13337+afcb49ec
Package less than 4.5.10-4.module+el8.6.0+13337+afcb49ec
Package less than 4.4.12-3.module+el8.6.0+13337+afcb49ec
Which are affected if the issue is related to RHSA 4797, but according to our investigation we have packages installed that fall under RHSA 4798, for which we have up-to-date packages installed.
We're running on-premise installation in version 4.3.8 on Manager and Agents.
Unfortunately I cannot give any details nor output from the systems as we're running security critical environment for services that cannot be disclosed.
My question is, would it be possible that for whatever reson, the vulnerability scanner cannot differentiate correctly the system setup in relation to the CVE / RHSAs?
We should be able to fix the issue, but as explained we really cannot do anything. And due to the aforementioned reasons our policy is to install packages only from approved repository sources and not to tinker with direct installs of updates (unless utmost importance decided separately).
Thanks for the good product you have, and looking foward to hear your comments.
BR, Antti