You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The general idea is similar to issue #165 that is already mostly fixed.
Steps to reproduce:
Create a regular reverse mount point
Create a file "test" in the original directory
Access the corresponding encrypted directory in the mount point (ls <encrypted dir>)
Quickly delete the file in the original data - instead create a device node
Access the file again, it will access the device node and attempt to read from it
In practice the impact of this possible attack is relatively small because step 4 already requires root permissions. Nevertheless, if I don't miss anything the problem can be easily avoided by checking the file type using the handle after the OpenNofollow call. Actually, there already is an Fstat call in the corresponding function.
The text was updated successfully, but these errors were encountered:
slackner
added a commit
to slackner/gocryptfs
that referenced
this issue
Dec 11, 2017
Steps to reproduce:
* Create a regular reverse mount point
* Create a file "test" in the original directory
* Access the corresponding encrypted directory in the mount point (ls <encrypted dir>)
* Quickly delete the file in the original data - instead create a device node
* Access the file again, it will access the device node and attempt to read from it
Fixesrfjakob#187
Steps to reproduce:
* Create a regular reverse mount point
* Create a file "test" in the original directory
* Access the corresponding encrypted directory in the mount point (ls <encrypted dir>)
* Quickly delete the file in the original data - instead create a device node
* Access the file again, it will access the device node and attempt to read from it
Fixes#187
The general idea is similar to issue #165 that is already mostly fixed.
Steps to reproduce:
ls <encrypted dir>
)In practice the impact of this possible attack is relatively small because step 4 already requires root permissions. Nevertheless, if I don't miss anything the problem can be easily avoided by checking the file type using the handle after the
OpenNofollow
call. Actually, there already is anFstat
call in the corresponding function.The text was updated successfully, but these errors were encountered: