Ping Identity PingAuthorize
Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 10.2.0.9
- >= 10.3, < 10.3.0.6
- >= 11.0, < 11.0.0.4
- >= 11.1, < 11.1.0.1
Fixed in 10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1
Mitigation
Upgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags.
Workaround
As a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution.
References
- Vendor advisory support.pingidentity.com/s/article/SECADV057-PingAuthorize-C…
- Release notes docs.pingidentity.com/pingauthorize/11.1/release_notes/pa…
- Release notes docs.pingidentity.com/pingauthorize/11.0/release_notes/pa…
2 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.