diff options
author | Michael Pratt <mpratt@google.com> | 2019-04-09 12:51:13 -0700 |
---|---|---|
committer | Michael Pratt <michael@prattmic.com> | 2019-04-09 13:49:00 -0700 |
commit | 3513350de63079505a1ad142942cc50ae8e511dc (patch) | |
tree | 7d82630fb76a9648fa3905e0ed70906195aae21e /content/docs/architecture_guide | |
parent | 37433204a8ecda68ea2164315686006240bf11aa (diff) |
Specify /proc explicitly
Diffstat (limited to 'content/docs/architecture_guide')
-rw-r--r-- | content/docs/architecture_guide/security.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content/docs/architecture_guide/security.md b/content/docs/architecture_guide/security.md index fc2a7bf7a..93723727c 100644 --- a/content/docs/architecture_guide/security.md +++ b/content/docs/architecture_guide/security.md @@ -37,8 +37,8 @@ might involve some combination of the following: 1. Racing with multiple threads in order to hit specific code paths. For example, for the [Dirty Cow][dirtycow] privilege escalation bug, an -application would open a specific file in proc or use a specific `ptrace` system -call, and use multiple threads in order to trigger a race condition when +application would open a specific file in `/proc` or use a specific `ptrace` +system call, and use multiple threads in order to trigger a race condition when touching a fresh page of memory. The attacker then gains control over a page of memory belonging to the system. With additional privileges or access to privileged data in the kernel, an attacker will often be able to employ |