Bug #69151 - mb_ereg should reject ill-formed byte sequence#1131
Closed
masakielastic wants to merge 3 commits intophp:masterfrom
masakielastic:mb_ereg
Closed
Bug #69151 - mb_ereg should reject ill-formed byte sequence#1131masakielastic wants to merge 3 commits intophp:masterfrom masakielastic:mb_ereg
masakielastic wants to merge 3 commits intophp:masterfrom
masakielastic:mb_ereg
Conversation
|
Can one of the admins verify this patch? |
|
Merged to master. Thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request add validation for encoding. Some of ill-formed byte sequence can be converterted to dangerous ascii characters by legacy UTF-8 decoder without checking trailing bytes.
htmlspecharcharsand PCRE functions reject them. Unicode Security Guide shows example. "C2 22 3C" can be treated as "C2 22" + "3C". "3C" means "<".