Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Resource type:
elb_desync_mitigation_modeProvider: AWS
Service:
elbSeverity: MEDIUM
Resource type:
AwsElbLoadBalancerWhat this check verifies
Classic Load Balancerdesync_mitigation_mode is evaluated to determine whether it is configured as defensive or strictest. Any other mode (such as monitor) is identified for attention.
Risk
Without strict desync mitigation, HTTP request smuggling can occur, enabling:- Cache/queue poisoning (integrity)
- Session hijacking and data exposure (confidentiality)
- Unintended backend actions and abuse (availability)
Recommendation
Set CLB desync mitigation todefensive or, where compatible, strictest. Validate in staging to avoid client breakage. Apply defense in depth: enforce strict header handling, pair with WAF controls, and monitor non-compliant request indicators.
Remediation
- CLI
- Terraform
- Dashboard steps
References
- https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-desync-mitigation-mode.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/elb-controls.html#elb-14
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/ELB/enable-configure-desync-mitigation-mode.html
- https://support.icompaas.com/support/solutions/articles/62000233337-ensure-classic-load-balancer-is-configured-with-defensive-or-strictest-desync-mitigation-mode
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = elb_desync_mitigation_mode. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks