elasticsearch: executing async search improperly stores HTTP headers leading to information disclosure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Elastic | Elasticsearch | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| RHAF Camel-K 1.8 | |||
| elasticsearch | cpe:/a:redhat:integration:1 | RHSA-2022:6407 | 2022-09-09T00:00:00Z |
| RHINT Camel-Q 2.7 | |||
| elasticsearch | cpe:/a:redhat:camel_quarkus:2.7 | RHSA-2022:5606 | 2022-07-19T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-0610 | Elasticsearch versions 7.7.0 to 7.10.1 contain an information disclosure flaw in the async search API. Users who execute an async search will improperly store the HTTP headers. An Elasticsearch user with the ability to read the .tasks index could obtain sensitive request headers of other users in the cluster. This issue is fixed in Elasticsearch 7.10.2 |
Github GHSA |
GHSA-5fvx-2jj3-6mff | Insufficiently Protected Credentials in Elasticsearch |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.222% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.