Vulnerability: Memory Corruption in libphonenumber AsYouTypeFormatter:AttemptToExtractIdd #3924
Conversation
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
…::AttemptToExtractIdd
tvislavski
approved these changes
Oct 9, 2025
kkeshava
approved these changes
Oct 9, 2025
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.
The memory corruption occurs because the parsing logic fails to pass the normalized character into accrued_input_without_formatting_ when the number starts with special characters during IDD extraction. This results in the tempSubString operation encountering the unnormalized special character's byte sequence, which is misinterpreted as a negative value, leading to a size or index error that causes memory corruption.
To fix the issue, pass the normalized character into accrued_input_without_formatting_.