Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ping Identity | PingAuthorize | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ping Identity | Pingauthorize |
|
Vendor Solution
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.
Vendor 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.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.445% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ping Identity
Ping Identity pingauthorize |
|
| Vendors & Products |
Ping Identity
Ping Identity pingauthorize |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse | |
| Weaknesses | CWE-201 CWE-226 CWE-366 CWE-488 CWE-772 |
|
| References |
|
|
| Metrics |
cvssV4_0
|