Nessus
[Top] [All Lists]

Re: Possible signed/unsigned confusion in plugin 22529

To: Nessus List <nessus@list.nessus.org>
Subject: Re: Possible signed/unsigned confusion in plugin 22529
From: Renaud Deraison <deraison@nessus.org>
Date: Fri, 10 Nov 2006 11:29:53 -0500
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: nessus@list.nessus.org
In-reply-to: <200611091634.kA9GYTCe016708@cfa0.cfa.harvard.edu>
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: <200611091634.kA9GYTCe016708@cfa0.cfa.harvard.edu>
Sender: nessus-bounces@list.nessus.org

On Nov 9, 2006, at 11:34 AM, Bob Babcock wrote:

Windows Nessus scanning Windows machines.
I'm seeing plugin 22529 triggering when I don't think it should.
In smb_nt_ms06-056.nasl, I see an if test for
  v[2] < 50727
I added a security_note call to print out the values of the v array and got
v[2]=-14809.  Looks like a signed/unsigned 16-bit int confusion.

We have identified the problem and are working on a fix. This only affects the Windows version of Nessus, for which we'll put out a new build as soon as possible.


Thanks,

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

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