Fix bash 2.05b detection #42
Open
Conversation
This file contains 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
GNU bash 2.05b does not do “{1..3}” expansion, which leads to mis-detecting
a fully patched bash on Debian sarge (my own packages) as vulnerable to
CVE-2014-7187 and missing CVE-2014-7187; expand those bashisms to keep
compatible and return correct values even for that version of GNU bash.
|
I’m removing the now-redundant repository. I merged bashcheck in its entirety, including my own patch, into my shellsnippets repository: |
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.
GNU bash 2.05b does not do “{1..3}” expansion, which leads to mis-detecting
a fully patched bash on Debian sarge (my own packages) as vulnerable to
CVE-2014-7187 and missing CVE-2014-7187; expand those bashisms to keep
compatible and return correct values even for that version of GNU bash.