← Back to team overview

touch-packages team mailing list archive

[Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

 

This bug was fixed in the package apport - 2.17.1-0ubuntu1

---------------
apport (2.17.1-0ubuntu1) vivid; urgency=medium

  * New upstream bug fix release:
    - SECURITY UPDATE: Fix root privilege escalation through crash forwarding
      to containers.
      Version 2.13 introduced forwarding a crash to a container's apport. By
      crafting a specific file system structure, entering it as a namespace
      ("container"), and crashing something in it, a local user could access
      arbitrary files on the host system with root privileges.
      Thanks to Stéphane Graber for discovering and fixing this!
      (CVE-2015-1318, LP: #1438758)
    - apport-kde tests: Fix imports to make tests work again.
    - Fix UnicodeDecodeError on parsing non-ASCII environment variables.
    - apport: use the proper pid when calling apport in another PID namespace.
      Thanks Brian Murray. (LP: #1300235)
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Tue, 14 Apr 2015 09:10:17 -0500

** Changed in: apport (Ubuntu)
       Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1318

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1300235

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in apport package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Test Case
  ---------
  1) Set your default browser to Chromium.
  2) Launch synaptic
  3) Click on the home page url for a package.
  4) Observe chromium-browser not launch
  5) Receive apport crash dialog
  5) Also notice the apport crash dialog refers to upstart / systemd

  none

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: => 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:

  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1300235/+subscriptions