Open Bug 1761134 Opened 2 years ago Updated 2 years ago

Consider filtering getsockopt/setsockopt in content process sandbox

Categories

(Core :: Security: Process Sandboxing, enhancement, P3)

Product:
Core
Component:
Security: Process Sandboxing
Platform:
Unspecified
Linux
Type:
enhancement

Tracking

()

People

(Reporter: jld, Unassigned)

Details

Currently we allow getsockopt and setsockopt with any arguments in sandboxed content processes on Linux, but (similarly to ioctl or prctl) there may be value in restricting the options that can be accessed.

Severity: -- → S4
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.