-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[BUG] CVE-2025-22227: Authentication Leak On Redirect With Reactor Netty HTTP Client #46206
Copy link
Copy link
Closed
Labels
Azure.Coreazure-coreazure-coreHttpClientcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Metadata
Metadata
Assignees
Labels
Azure.Coreazure-coreazure-coreHttpClientcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
Describe the bug
There's a CVE-2025-22227 for azure sdk for java in the dependency reactor-http-netty. Reactor-netty-http 1.0.48 is used by the sdk. It seems that there's a version 1.0.49 available but only in spring with a commercial license.
It would be good to have a new version without going to the latest version 1.2.x of the reactor-netty-http since it needs a more recent netty version and it can break applications that are stuck with an earlier netty version (it's my case).
Another question would be if this CVE affects in any way the azure sdk. Maybe the sdk client doesn't follow redirects