[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
This bug was fixed in the package sudo - 1.7.2p1-1ubuntu5.5
---
sudo (1.7.2p1-1ubuntu5.5) lucid-proposed; urgency=low
* toke.{cl}: avoid duplicate fclose() of the sudoers file (LP: #553786)
- http://www.sudo.ws/repos/sudo/rev/164d39108dde
-- Marc Deslauriers marc.deslauri...@ubuntu.com Thu, 22 Nov 2012 16:08:01
-0500
** Changed in: sudo (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553786
Title:
*** glibc detected *** sudo: double free or corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
After installing sudo package from proposed, there is no longer crash: sudo ls sudo: /etc/sudoers.d/mama is mode 0644, should be 0440 /etc/sudoers.d/README: /etc/sudoers.d/mama near line 18 sudo: parse error in /etc/sudoers.d/README near line 18 sudo: no valid sudoers sources found, quitting Verified. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Hello Daniel, or anyone else affected, Accepted sudo into lucid-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/sudo/1.7.2p1-1ubuntu5.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: sudo (Ubuntu Lucid) Status: Confirmed = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
** Branch linked: lp:ubuntu/lucid-proposed/sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
I have been hit by this bug and it's *extremely nasty*. I am instantly locked out of my system with no way of fixing it. Things like these MUST NOT happen. I get from this bugreport that there is a fix. BACKPORT THIS FIX TO LUCID! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Upstream fix: http://www.sudo.ws/repos/sudo/rev/164d39108dde ** Also affects: sudo (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu Lucid) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
** Description changed: - Binary package hint: sudo + [SRU] - Lucid beta1, sudo 1.7.2p1-1ubuntu4. I added a file with incorrect - permissions under /etc/sudoers.d/, and while that needed fixing, sudo(8) - certainly shouldn't react like this: + [Impact] + Lucid users who create a file in /etc/sudoers.d with incorrect permissions cause sudo to segfault, preventing them from using sudo to change the permissions. + + [Test case] + 1- Create a file in /etc/sudoers.d with 644 permissions + 2- Attempt to use sudo + 3- sudo should simply print a warning, and not segfault + + [Regression potental] + This is the upstream patch that has been used for quite a while, and has passed the qa-regression-testing test suite. If there are regressions, I suppose it could be in the sudoers file handling. + + + Original description: + Lucid beta1, sudo 1.7.2p1-1ubuntu4. I added a file with incorrect permissions under /etc/sudoers.d/, and while that needed fixing, sudo(8) certainly shouldn't react like this: $ sudo bash sudo: /etc/sudoers.d/admin is mode 0644, should be 0440 /etc/sudoers.d/README: /etc/sudoers.d/admin near line 18 sudo: parse error in /etc/sudoers.d/README near line 18 sudo: no valid sudoers sources found, quitting *** glibc detected *** sudo: double free or corruption (!prev): 0x0861b7b0 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6(+0x6b581)[0xa3a581] /lib/tls/i686/cmov/libc.so.6(+0x6cdd8)[0xa3bdd8] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0xa3eebd] /lib/tls/i686/cmov/libc.so.6(fclose+0x14a)[0xa2aa9a] sudo[0x805782d] sudo[0x80587c6] sudo[0x805639e] sudo[0x805a104] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x9e5bd6] sudo[0x804a7c1] === Memory map: 002b1000-002b7000 r-xp 08:07 16579 /lib/tls/i686/cmov/libnss_compat-2.11.1.so 002b7000-002b8000 r--p 6000 08:07 16579 /lib/tls/i686/cmov/libnss_compat-2.11.1.so 002b8000-002b9000 rw-p 7000 08:07 16579 /lib/tls/i686/cmov/libnss_compat-2.11.1.so 003bf000-003c9000 r-xp 08:07 16581 /lib/tls/i686/cmov/libnss_files-2.11.1.so 003c9000-003ca000 r--p 9000 08:07 16581 /lib/tls/i686/cmov/libnss_files-2.11.1.so 003ca000-003cb000 rw-p a000 08:07 16581 /lib/tls/i686/cmov/libnss_files-2.11.1.so 0045f000-00467000 r-xp 08:07 16583 /lib/tls/i686/cmov/libnss_nis-2.11.1.so 00467000-00468000 r--p 7000 08:07 16583 /lib/tls/i686/cmov/libnss_nis-2.11.1.so 00468000-00469000 rw-p 8000 08:07 16583 /lib/tls/i686/cmov/libnss_nis-2.11.1.so 00542000-0055f000 r-xp 08:07 16364 /lib/libgcc_s.so.1 0055f000-0056 r--p 0001c000 08:07 16364 /lib/libgcc_s.so.1 0056-00561000 rw-p 0001d000 08:07 16364 /lib/libgcc_s.so.1 0060b000-0060c000 r-xp 00:00 0 [vdso] 006e6000-006e8000 r-xp 08:07 16575 /lib/tls/i686/cmov/libdl-2.11.1.so 006e8000-006e9000 r--p 1000 08:07 16575 /lib/tls/i686/cmov/libdl-2.11.1.so 006e9000-006ea000 rw-p 2000 08:07 16575 /lib/tls/i686/cmov/libdl-2.11.1.so 0084e000-00869000 r-xp 08:07 16304 /lib/ld-2.11.1.so 00869000-0086a000 r--p 0001a000 08:07 16304 /lib/ld-2.11.1.so 0086a000-0086b000 rw-p 0001b000 08:07 16304 /lib/ld-2.11.1.so 008a5000-008ae000 r-xp 08:07 16574 /lib/tls/i686/cmov/libcrypt-2.11.1.so 008ae000-008af000 r--p 8000 08:07 16574 /lib/tls/i686/cmov/libcrypt-2.11.1.so 008af000-008b rw-p 9000 08:07 16574 /lib/tls/i686/cmov/libcrypt-2.11.1.so - 008b-008d7000 rw-p 00:00 0 + 008b-008d7000 rw-p 00:00 0 009cf000-00b22000 r-xp 08:07 16572 /lib/tls/i686/cmov/libc-2.11.1.so 00b22000-00b23000 ---p 00153000 08:07 16572 /lib/tls/i686/cmov/libc-2.11.1.so 00b23000-00b25000 r--p 00153000 08:07 16572 /lib/tls/i686/cmov/libc-2.11.1.so 00b25000-00b26000 rw-p 00155000 08:07 16572 /lib/tls/i686/cmov/libc-2.11.1.so - 00b26000-00b29000 rw-p 00:00 0 + 00b26000-00b29000 rw-p 00:00 0 00c5d000-00c68000 r-xp 08:07 16381 /lib/libpam.so.0.82.2 00c68000-00c69000 r--p a000 08:07 16381 /lib/libpam.so.0.82.2 00c69000-00c6a000 rw-p b000 08:07 16381 /lib/libpam.so.0.82.2 00e4f000-00e62000 r-xp 08:07 16578 /lib/tls/i686/cmov/libnsl-2.11.1.so 00e62000-00e63000 r--p 00012000 08:07 16578 /lib/tls/i686/cmov/libnsl-2.11.1.so 00e63000-00e64000 rw-p 00013000 08:07 16578 /lib/tls/i686/cmov/libnsl-2.11.1.so - 00e64000-00e66000 rw-p 00:00 0 + 00e64000-00e66000 rw-p 00:00 0 08048000-08066000 r-xp 08:07 573495 /usr/bin/sudo 08066000-08067000 r--p 0001d000 08:07 573495 /usr/bin/sudo 08067000-08068000 rw-p 0001e000 08:07 573495 /usr/bin/sudo - 08068000-0806b000 rw-p 00:00 0 + 08068000-0806b000 rw-p 00:00 0 08612000-08633000
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
This bug appears to be fixed in precise. A message is output about the wrong permissions, but sudo itself works correctly. ** Changed in: sudo (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Has Ubuntu changed its meaning of LTS? This issue still exists in Lucid. Keith Baker already pointed out that the issue was fixed at least as early as Natty. Can we get the fix back-ported to Lucid? Is there any reason this shouldn't be considered critical as it can lock out legitimate administrative users with no workaround except to run recovery (in some scenarios)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
I've just been bitten by this bug yet again. I've had to request to my administrator to reboot our server into recovery mode to remove the file. Why isn't a bug that locks administrators out of the operating system (in an otherwise well-configured environment) not considered a critical bug? The only workaround I can think of is to know in advance that creating a file in /etc/sudoers.d might cause lockouts, so keep a separate shell as root... but I don't always remember to do that. I would be grateful if someone would please fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Tried same thing on desktop version of natty. There the problem seems fixed. Still I'd consider this bug critical since lucid is the current long- term-support version. ** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Just happened to me on a fresh and updated lucid server installation. This is really annoying since the server was a plain router. No keyboard or monitor was connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
How do you change the file rights if sudo doesn't work nor you have a root password set nor you have direct access to the server to reboot into single mode? IMHO, this bug should be set as CRITICAL, given that you are banned from administrate a remote server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553786 Title: *** glibc detected *** sudo: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/553786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553786] Re: *** glibc detected *** sudo: double free or corruption
Confirmed also on Ubuntu 10.4 - 1.7.2p1-1ubuntu5.2 . Changing the file rights from 644 to 440 fixed it. -- *** glibc detected *** sudo: double free or corruption https://bugs.launchpad.net/bugs/553786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
