New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 800279 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Security



Sign in to add a comment

CVE-2017-17807 CrOS: Vulnerability reported in Linux kernel

Project Member Reported by vomit.go...@appspot.gserviceaccount.com, Jan 9 2018

Issue description

VOMIT (go/vomit) has received an external vulnerability report for the Linux kernel. 

Advisory: CVE-2017-17807
  Details: http://vomit.googleplex.com/advisory?id=CVE/CVE-2017-17807
  CVSS severity score: 2.1/10.0
  Description:

The KEYS subsystem in the Linux kernel before 4.14.6 omitted an access-control check when adding a key to the current task's "default request-key keyring" via the request_key() system call, allowing a local user to use a sequence of crafted system calls to add keys to a keyring with only Search permission (not Write permission) to that keyring, related to construct_get_dest_keyring() in security/keys/request_key.c.



This bug was filed by http://go/vomit
Please contact us at vomit-team@google.com if you need any assistance.

 
Labels: Security_Severity-Low Security_Impact-Stable Pri-2
Owner: groeck@chromium.org
Status: Assigned (was: Untriaged)
Upstream 4dca6ea1d94320 ("KEYS: add missing permission check for request_key() destination"). Already fixed in chromeos-4.4 and chromeos-4.14 with stable release merges. May fix in chromeos-3.18. No plan to push into stable releases due to low severity.

Labels: M-65
Cc: wonderfly@google.com
Status: WontFix (was: Assigned)
chrmomeos-3.18 merge attempt results in conflicts. Given the low severity and the risk of introducing problems due to the merge conflicts, won't apply to 3.18 and earlier.

Cc: sawlani@google.com

Sign in to add a comment