pptp crashed with SIGSEGV on login

Bug #978569 reported by kapetr
72
This bug affects 15 people
Affects Status Importance Assigned to Milestone
network-manager-pptp
New
Undecided
Unassigned
pptp-linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

On every boot of U12.04 I get window with: +- "Problem with system program"
I have to (?) enter root password -> then bug report is generated.

I have configured 2 PPTP VPNs in NM - but without automatic run.
After I defined them i had test them successful - but now is running of VPN in NM not accessible.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pptp-linux 1.7.2-6
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sat Apr 7 16:16:23 2012
ExecutablePath: /usr/sbin/pptp
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120401)
ProcCmdline: /usr/sbin/pptp 69.61.14.2 --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-2582
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pptp-linux
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: pptp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
kapetr (kapetr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pptp-linux (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
kapetr (kapetr) wrote :

What I am wondering about is - WHY is the command /usr/sbin/pptp 69.61.14.2 --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-2582 executed at all ?!

The IP 69.61.14.2 belongs to the one VPN defined in NM - but as I wrote: it is not configured to be run automatically.

visibility: private → public
visibility: public → private
kapetr (kapetr)
visibility: private → public
Revision history for this message
kapetr (kapetr) wrote :

Can this not be a security problem if something (NM ?) tries to open VPN tunnel without asking for it ?

I'm marking this bug as security vulnerability - if it is not a security problem (I don't understand it) then tell me and I will clear this flag again.

Thanks.

security vulnerability: no → yes
Revision history for this message
kapetr (kapetr) wrote :

Note: after $ sudo killall NetworkManager

the NM comes up again, but now with VPN in menu (and working).
That mean - only on boot/login is the problem.

security vulnerability: yes → no
security vulnerability: yes → no
Revision history for this message
kapetr (kapetr) wrote :

... some comment would be helpful <jdstrand> :-/

If something redirect all network flow without asking, without be configured to do so ...
... if such thing is not a security issue, what then ?

BTW - after next updates the problem is disappeared - but maybe is it while all my VPNs are now set not for all users:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/comments/6

security vulnerability: no → yes
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

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.

security vulnerability: yes → no
security vulnerability: yes → no
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pptp-linux (Ubuntu):
status: New → Confirmed
tags: added: trusty
Revision history for this message
stakasha (d-v-razumov) wrote :

This bug also affects Ubuntu 13.10, 32bit.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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