PingAuthorize data exposure via late Gateway responses
Ping Identity PingAuthorize
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Ping Identity PingAuthorize |
| No fix yet |
Original description
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.