History log of /PHP-8.2/ext/pcre/tests/preg_replace_callback_array_fatal_error.phpt (Results 1 – 4 of 4)
Revision Date Author Comments
# f39b5c4c 11-Oct-2023 Ilija Tovilo

Close PHP tags in tests

Closes GH-12422


# cda7e8f1 23-Jun-2022 Ilija Tovilo

Replace another hard-coded line number


# 9bfdfcac 23-Jun-2022 Ilija Tovilo

Replace more hard-coded line numbers


# 5bb3e233 24-Apr-2022 tobil4sk

Implement #77726: Allow null character in regex patterns

In 8b3c1a3, this was disallowed to fix #55856, which was a security
issue caused by the /e modifier. The fix that was made was th

Implement #77726: Allow null character in regex patterns

In 8b3c1a3, this was disallowed to fix #55856, which was a security
issue caused by the /e modifier. The fix that was made was the
"Easier fix" as described in the original report.

With this fix, pattern strings are no longer treated as null terminated,
so null characters can be placed inside and matched against with regex
patterns without security problems, so there is no longer a reason to
give the error. Allowing this is consistent with the behaviour of many
other languages, including JavaScript, and thanks to PCRE2[0], it does
not require manually escaping null characters. Now that we can avoid the
error here without the cost of escaping characters, there is really no
need anymore to stray here from the conventional behaviour.

Currently, null characters are still disallowed before the first
delimiter and in the options section at the end of a regex string, but
these error messages have been updated.

[0] Since PCRE2, pattern strings no longer have to be null terminated,
and raw null characters match as normal.

Closes GH-8114.

show more ...