-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix GH-17139: Fix zip_entry_name() crash on invalid entry. #17142
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 all commits
Commits
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,19 @@ | ||
--TEST-- | ||
GH-17139 - zip_entry_name() crash | ||
--EXTENSIONS-- | ||
zip | ||
--FILE-- | ||
<?php | ||
$zip = zip_open(__DIR__."/test_procedural.zip"); | ||
if (!is_resource($zip)) die("Failure"); | ||
// no need to bother looping over, the entry name should point to a dangling address from the first iteration | ||
$zip = zip_read($zip); | ||
var_dump(zip_entry_name($zip)); | ||
?> | ||
--EXPECTF-- | ||
Deprecated: Function zip_open() is deprecated in %s on line %d | ||
|
||
Deprecated: Function zip_read() is deprecated in %s on line %d | ||
|
||
Deprecated: Function zip_entry_name() is deprecated in %s on line %d | ||
string(3) "foo" |
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.
This might lead to a memory leak. Wouldn't the refcount increase for every
zip_read()
?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.
ASAN nor DEBUG build reported anything on this new test nor in zip_read.phpt
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.
Argh – resources! For a clean solution, the
le_zip_entry
resources would need to store a reference to theirle_zip_dir
resource; otherwise, as happens here, if thele_zip_dir
resource is closed, there are dangling pointers. Increasing the refcount here (and possibly elsewhere) only shades the problem. Given that the procedural API is deprecated as of PHP 8.0.0, I'd opt for wontfix. @remicollet, what do you think?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.
If that s obsolete for that long, might be best remove it for 8.5/9.0 or so many people still using this api ?
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.
I think the plan is to remove for PHP 9 (removing in a minor is quite a BC break). And I guess most are using the OO-API already.