feat(elb): add new check elb_desync_mitigation_mode
#5500
Merged
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.
Context
Add a new check to ensure Classic Load Balancers are configured with either the defensive or strictest desync mitigation mode to prevent HTTP desynchronization issues. This control fails if the desync mitigation mode does not use one of these modes.
HTTP desync vulnerabilities can lead to serious security risks like request smuggling, credential hijacking, and unauthorized command execution. Enabling defensive or strictest desync mitigation modes helps protect applications from these risks by safeguarding against potential desynchronization attacks.
Description
Changed elb service to add a new attribute
desync_mitigation_mode
toLoadBalancer
model. Added a new checkelb_desync_mitigation_mode
with respective unit tests.Checklist
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.