Repository navigation
Conversation
DateTime::createFromFormat() accepts offsets like +9999, whose name does not fit the fixed-size buffer: snprintf() truncated it, and the returned length overran the allocation, so the string was missing its terminating NUL. phpGH-9763 only rejected such offsets in the DateTimeZone constructor.
TimWolla
approved these changes
Nov 14, 2026
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.
DateTime::createFromFormat()accepts offsets like +9999, whose name does not fit the fixed-size buffer: snprintf() truncated it, and the returned length overran the allocation, so the string was missing its terminating NUL. GH-9763 only rejected such offsets in theDateTimeZoneconstructor.It's not really the correct offset, but it should be fixed in timelib. This is fix only for PHP side.