-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Doc Repo] Fix path traversal security issue #3678
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not tested but eliminate use of forged data.
Suggest a "Security" label for security fix
@PapillonMcGill I agree that a Security label should be created. I'll put it in the LORIS meeting agenda. |
@@ -78,6 +78,7 @@ | |||
|
|||
|
|||
$target_path = $base_path . $fileBase; | |||
error_log("Target path is: $target_path"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left over debug statement.. this shouldn't be in the error log.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
See Redmine #14511.
Related to #3603, which contains a better fix + more significant refactoring.
This PR provides the minimal changes necessary to fix the vulnerability.