Nessus
[Top] [All Lists]

Re: Re-released Microsoft Patches.

To: nessus@lists.nessus.org
Subject: Re: Re-released Microsoft Patches.
From: Renaud Deraison <deraison@nessus.org>
Date: Fri, 10 Nov 2006 10:40:15 -0500
Cc:
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: nessus@lists.nessus.org
In-reply-to: <169658C0C845EC438759DB8B8BC7065403BC05E1@NOC-EXCH1.24hourfit.com>
List-archive: <http://mail.nessus.org/pipermail/nessus>
List-help: <mailto:nessus-request@list.nessus.org?subject=help>
List-id: Discussion of Nessus software <nessus.list.nessus.org>
List-post: <mailto:nessus@list.nessus.org>
List-subscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=subscribe>
List-unsubscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=unsubscribe>
References: <169658C0C845EC438759DB8B8BC7065403BC05E1@NOC-EXCH1.24hourfit.com>
Sender: nessus-bounces@list.nessus.org

On Nov 10, 2006, at 10:31 AM, John Scherff wrote:

We are having a similar problem, but in reverse. In some cases, Nessus will report that a patch is missing, but the patch has been superseded by another patch which HAS been applied. The same thing also sometimes occurs when a patch is rolled into a service pack.

Nessus has the appropriate logic to detect superseded patches -- make sure your plugins are up-to-date.

Also, if you give it admin credentials, then a file version check will be done, hence nullyfing the risk of wrongly detecting a superseded patch.


I'd be interested in the specific list of patches which you say create false positives and knowing how recent your plugin set it.



                                        -- Renaud
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>