Hi, On 10.01.2018 11:12, Christian Reiter wrote: > Does anybody know if this is a local problem which I can solve or if there is > anything else which I can do?
unfortunately some Firefox versions tend to leave registry entries behind causing such false detection. We did a few tests on this and could confirm your observations: A base install of Firefox 56.0 in 32-bit will be upgraded first to 57.0 including a migration to a 64-bit version of Firefox. After a restart a new update to 57.0.4 will be offered and a second restart is required. As a result the following registry key wasn't deleted by the upgrade / migration routine: HKLM\SOFTWARE\Wow6432Node\mozilla.org\Mozilla -> CurrentVersion -> 56.0 causing a detection of Firefox 57.0.4 AND 56.0. On the other hand a base install of Firefox 56.0.2 in 32-bit will be upgraded directly to 57.0.4 including a migration to a 64-bit version of Firefox. In this case the upgrade / migration routine is removing the old registry entry correctly and only Firefox 57.0.4 is detected. Unfortunately there is not that much we can do from NVT side if a software is behaving inconsistently like this and you would need to clean up the left-over registry keys from the registry. Regards, -- Christian Fischer | PGP Key: 0x54F3CE5B76C597AD Greenbone Networks GmbH | http://greenbone.net Neumarkt 12, 49074 Osnabrück, Germany | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
