Dio
Dio: Cross-origin redirect leaks sensitive request headers in `dio_http2_adapter`
Dio is a powerful HTTP client for Dart and Flutter. From 1.0.0 until 2.8.0, dio_http2_adapter follows redirects in Http2Adapter._fetch by copying the original RequestOptions.headers into the redirected HTTP/2 request without comparing the source and destination origins. A server contacted by an application can return a cross-origin Location redirect to a different-origin destination, which then receives preserved Authorization, Cookie, and Proxy-Authorization headers because RequestOptions.copyWith retains the full header map. The issue applies when applications use Http2Adapter for authenticated requests, and redirect following is enabled by default. This issue is fixed in version 2.8.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.0.0, < 2.8.0
Fixed in 2.8.0
Mitigation
Upgrade dio to 2.8.0 or later.
References
- Vendor advisory github.com/cfug/dio/security/advisories/GHSA-c…
- Patch github.com/cfug/dio/commit/9d7ac913340084f3b49…
- Release notes github.com/cfug/dio/releases/tag/http2_adapter…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.