Nmap Development mailing list archives

Re: --excludefile causing reads in free()'d memory

From: Richard Moore <rich () westpoint ltd uk>
Date: Mon, 09 Mar 2009 16:41:35 +0000

David Fifield wrote:

The bug is that TargetGroup::parse_expr calls strtok also and messes up
the global strtok state. parse_expr makes strtok look at the strduped
memory and load_exclude continues looking at it. This creates a bug,
which is that only the first specification on each line of the file is
honored.


You could try switching to strtok_r on unix and strtok_s on Windows
which are reentrant.

Cheers

Rich.

-- 
Richard Moore, Principal Software Engineer,
Westpoint Ltd,
Albion Wharf, 19 Albion Street, Manchester, M1 5LN, England
Tel: +44 161 237 1028
Fax: +44 161 237 1031

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org

Current thread:

--excludefile causing reads in free()'d memory Brandon Enright (Mar 05)
- Re: --excludefile causing reads in free()'d memory David Fifield (Mar 09)
  - Re: --excludefile causing reads in free()'d memory Richard Moore (Mar 09)
  - Re: --excludefile causing reads in free()'d memory Brandon Enright (Mar 15)
    - Re: --excludefile causing reads in free()'d memory David Fifield (Mar 16)