crash in supplicant_interface_init because of unsafe strcmp

Bug #181232 reported by Alexander Sack
4
Affects Status Importance Assigned to Milestone
NetworkManager
Unknown
Critical
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Steps to reproduce:
1. Click on the network manager to connect to 'UnEncrypted Network'

Stack trace:
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Device wlan0 activation
scheduled...
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation (wlan0)
started...
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) scheduled...
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) started...
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) scheduled...
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) complete.
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) starting...
Feb 26 16:20:41 mobile-2509 NetworkManager: <info> Activation
(wlan0/wireless): access point 'Guest' is unencrypted, no key needed.
Feb 26 16:20:42 mobile-2509 NetworkManager: <info> supplicant_interface_init()
- connect to global ctrl socket (0/10).
Feb 26 16:20:42 mobile-2509 NetworkManager: <info> supplicant_interface_init()
- connect to global ctrl socket (1/10).
Feb 26 16:20:42 mobile-2509 NetworkManager: <WARN> nm_signal_handler(): Caught
signal 11. Generating backtrace...
Feb 26 16:20:42 mobile-2509 NetworkManager: ******************* START
**********************************
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 0: /usr/sbin/NetworkManager
[0x806af01]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 1: /usr/sbin/NetworkManager
[0x806b066]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 2: [0xffffe420]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 3: /usr/sbin/NetworkManager
[0x80563aa]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 4: /usr/lib/libglib-2.0.so.0
[0xb7d71e73]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 5:
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x176) [0xb7d739b6]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 6: /usr/lib/libglib-2.0.so.0
[0xb7d76d0d]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 7:
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1dc) [0xb7d770fc]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 8: /usr/sbin/NetworkManager
[0x805741e]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 9: /usr/lib/libglib-2.0.so.0
[0xb7d955bb]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 10: /lib/libpthread.so.0
[0xb7ce2427]
Feb 26 16:20:42 mobile-2509 NetworkManager: Frame 11:
/lib/libc.so.6(clone+0x5e) [0xb7c6855e]
Feb 26 16:20:42 mobile-2509 NetworkManager: ******************* END
**********************************

Revision history for this message
RajiB (raji-linux) wrote :
Alexander Sack (asac)
Changed in network-manager:
status: New → Fix Committed
Changed in network-manager:
status: Unknown → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

this isn't an issue in latest hardy anymore.

Changed in network-manager:
status: Fix Committed → Fix Released
Changed in network-manager:
importance: Unknown → Critical
status: Invalid → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.