Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 10.2.0.9, 10.3.0.6, 11.0.0.4 and 1 more.
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Ping Identity | <10.2.0.9, >=10.3 <10.3.0.6, >=11.0 <11.0.0.4, >=11.1 <11.1.0.1 | 10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket