-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix GH-16802: open_basedir bypass using curl extension #16804
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
Closed
Closed
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
--TEST-- | ||
GH-16802 (open_basedir bypass using curl extension) | ||
--EXTENSIONS-- | ||
curl | ||
--SKIPIF-- | ||
<?php | ||
if (PHP_OS_FAMILY === "Windows") die("skip not for Windows"); | ||
$curl_version = curl_version(); | ||
if ($curl_version['version_number'] < 0x075500) { | ||
die("skip: blob options not supported for curl < 7.85.0"); | ||
} | ||
?> | ||
--INI-- | ||
open_basedir=/nowhere | ||
--FILE-- | ||
<?php | ||
$ch = curl_init("file:///etc/passwd"); | ||
curl_setopt($ch, CURLOPT_PROTOCOLS_STR, "all"); | ||
curl_setopt($ch, CURLOPT_PROTOCOLS_STR, "ftp,all"); | ||
curl_setopt($ch, CURLOPT_PROTOCOLS_STR, "all,ftp"); | ||
curl_setopt($ch, CURLOPT_PROTOCOLS_STR, "all,file,ftp"); | ||
var_dump(curl_exec($ch)); | ||
?> | ||
--EXPECTF-- | ||
Warning: curl_setopt(): The FILE protocol cannot be activated when an open_basedir is set in %s on line %d | ||
|
||
Warning: curl_setopt(): The FILE protocol cannot be activated when an open_basedir is set in %s on line %d | ||
|
||
Warning: curl_setopt(): The FILE protocol cannot be activated when an open_basedir is set in %s on line %d | ||
|
||
Warning: curl_setopt(): The FILE protocol cannot be activated when an open_basedir is set in %s on line %d | ||
bool(false) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Why not? The test passes for me (checked
master
only, though).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.
Because the file paths are Linux file paths. It passes because the check prevents the access anyway, but I didn't want to deal with Windows and check what happens if the patch is not applied. I can remove this check if you want.
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.
Without the patch, only the fourth
curl_setopt()
would trigger a warning, andcurl_exec()
would returnfalse
(withCURLOPT_VERBOSE
"Protocol "file" disabled" is reported). So the actual file:// URI wouldn't matter. Doingcurl_exec()
aftereach curl_setopt()
would only fail due to "Couldn't open file /etc/passwd" for the first exec; the three followingcurl_exec()
would fail due to "Protocol "file" disabled" (still without the patch).Anyhow, since the
open_basedir
value doesn't matter, we could use"file://" . str_replace("\\", "/", __FILE__)
instead offile://etc/passwd
, but it seems to me checking for the warnings is good enough. Even thecurl_exec()
is not really relevant.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.
Yes it is, because we want to check that the path is actually blocked, e.g. it could be broken in a way that warns but still allows the path.
Anyway I'll just drop the Windows skipif