Fix global config-backend snippet config #856
Merged
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
The mitigation of CVE-2021-25740 added a command-line option to allow a sysadmin to partially or completely remove backend configuration snippet. This option added a new code where there was only a straightforward assignment. This code fails on how to check if a configuration has a source and, instead of adjust the logging message, the whole assignment was being skipped. However a global configuration by definition doesn't have a source, leading to backend configuration snippet being skipped if not configured via ingress or service annotation. This fix should be merged up to v0.10.
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 mitigation of CVE-2021-25740 added a command-line option to allow a sysadmin to partially or completely remove backend configuration snippet. This option added a new code where there was only a straightforward assignment. This code fails on how to check if a configuration has a source and, instead of adjust the logging message, the whole assignment was being skipped. However a global configuration by definition doesn't have a source, leading to backend configuration snippet being skipped if not configured via ingress or service annotation.
This fix should be merged up to v0.10.