Opened 5 years ago

Closed 5 years ago

#15088 closed defect (fixed)

Add the wait4() syscall to the seccomp sandbox

Reported by: sanic Owned by:
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version: Tor:
Severity: Keywords: tor-relay seccomp 025-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Tor version seems to call wait4() upon receiving SIGHUP, and this violates the seccomp sandbox rules in sandbox.c, crashing the tor process.

Trace from tor's log on debug loglevel, right after /etc/init.d/tor reload:

============================================================ T= 1425215692
(Sandbox) Caught a bad syscall attempt (syscall wait4)
Mar 01 16:14:52.000 [info] cpuworker_main(): read request failed. Exiting.

The patch is as simple as adding wait4() to the whitelist:

diff -Naur tor-
--- tor-
@@ -119,6 +119,7 @@
+    SCMP_SYS(wait4),
 #ifdef __NR_fstat64

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by nickm

Keywords: tor-relay seccomp 025-backport added
Milestone: Tor: 0.2.6.x-final

comment:2 Changed 5 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.5.x-final

Merged to 0.2.6, marking for possible backport.

comment:3 Changed 5 years ago by nickm

(The branch is bug15088_025)

comment:4 Changed 5 years ago by nickm

Resolution: fixed
Status: newclosed

merged into 0.2.5.

Note: See TracTickets for help on using tickets.