nmap crashed with SIGSEGV in ultra_scan()

[kelargo]

Binary package hint: nmap

just upgraded to Jaunty... nmap is a security tool.. so checking to notify the security team.

root@machine:/home/user# nmap -sP 70.176.238.212

Starting Nmap 4.76 ( http://nmap.org ) at 2009-04-02 00:25 CDT
Segmentation fault (core dumped)
root@machine:/home/user#

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nmap
NonfreeKernelModules: fglrx
Package: nmap 4.76-0ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: nmap -sS -O 70.176.238.212
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=
 SHELL=/bin/bash
Signal: 11
SourcePackage: nmap
StacktraceTop:
 ?? ()
 ?? ()
 ultra_scan ()
 ?? ()
 nexthost ()
Title: nmap crashed with SIGSEGV in ultra_scan()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: libvirtd

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
ultra_scan ()
?? ()
nexthost ()

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
ultra_scan ()
?? ()
nexthost ()

[Jamie Strandboge (jdstrand)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[kelargo (kelong-2000)]

thank you. I was not sure if it was or not.

Kenneth Long

--- On Thu, 4/2/09, Jamie Strandboge <email address hidden> wrote:

> From: Jamie Strandboge <email address hidden>
> Subject: [Bug 353601] Re: nmap crashed with SIGSEGV in ultra_scan()
> To: <email address hidden>
> Date: Thursday, April 2, 2009, 12:11 PM
> Thanks for taking the time to report this bug and helping to
> make Ubuntu
> better. We appreciate the difficulties you are facing, but
> this appears
> to be a "regular" (non-security) bug. I have
> unmarked it as a security
> issue since this bug does not show evidence of allowing
> attackers to
> cross privilege boundaries nor directly cause loss of
> data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Attachment removed: "CoreDump.gz"
> http://launchpadlibrarian.net/24660096/CoreDump.gz
>
> ** Visibility changed to: Public
>
> ** This bug is no longer flagged as a security
> vulnerability
>
> --
> nmap crashed with SIGSEGV in ultra_scan()
> https://bugs.launchpad.net/bugs/353601
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “nmap” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: nmap
>
> just upgraded to Jaunty... nmap is a security tool.. so
> checking to notify the security team.
>
> root@machine:/home/user# nmap -sP 70.176.238.212
>
> Starting Nmap 4.76 ( http://nmap.org ) at 2009-04-02 00:25
> CDT
> Segmentation fault (core dumped)
> root@machine:/home/user#
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/nmap
> NonfreeKernelModules: fglrx
> Package: nmap 4.76-0ubuntu4
> ProcAttrCurrent: unconfined
> ProcCmdline: nmap -sS -O 70.176.238.212
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> LANGUAGE=
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: nmap
> StacktraceTop:
> ?? ()
> ?? ()
> ultra_scan ()
> ?? ()
> nexthost ()
> Title: nmap crashed with SIGSEGV in ultra_scan()
> Uname: Linux 2.6.28-11-generic x86_64
> UserGroups: libvirtd

[Chuck Short (zulcss)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Chuck Short (zulcss)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!