ext/soap: Fix SOAP xsd:hexBinary odd-length decoding#22698
Open
LamentXU123 wants to merge 1 commit into
Open
Conversation
devnexen
approved these changes
Jul 11, 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.
xsd:hexBinaryvalues must contain an even number of hexadecimal digits.However, previously we allocated
strlen(content) / 2bytes and decoded only complete byte pairs. As a result, an odd-length value such asABCwas accepted asab(what...?), silently ignoring the trailing nibble.Lets reject odd-length
xsd:hexBinaryvalues instead and throw an Error here which makes better sense. The error message is copied from other decoding errors. (I think in the future, we can make the decoding error message more useful, in bulk.)This is in master as a
stricter parsingPR