[4.5.x] Upgrade commons-codec to 1.15 due to vulnerability to Information Exposure#260
Closed
milczarekIT wants to merge 1 commit intoapache:4.5.xfrom
Closed
Conversation
…ncoded string into arbitrary value" https://issues.apache.org/jira/browse/CODEC-134
Member
|
I don't think that we use Base32, do we? |
Member
|
@michael-o Not only do we not use |
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
3 participants
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.
Fixed information exposure "Base32 would decode some invalid Base32 encoded string into arbitrary value" https://issues.apache.org/jira/browse/CODEC-134
This issue has been fixed in commons-codec 1.13, upgrading to the newest 1.15.
Version 5.0.x already have commons-codec 1.15
commons-codec versions [,1.13) are vulnerable to Information Exposure. When there is no byte array value that can be encoded into a string the Base32 implementation does not reject it, and instead decodes it into an arbitrary value which can be re-encoded again using the same implementation. This allows for information exposure exploits such as tunneling additional information via seemingly valid base 32 strings.