OpenSearch SQL plugin: Unsafe cursor deserialization permits server code execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| opensearch-project | sql | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Opensearch-project | Sql |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.499% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opensearch-project
Opensearch-project sql |
|
| Vendors & Products |
Opensearch-project
Opensearch-project sql |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenSearch SQL supports querying OpenSearch data using SQL and Piped Processing Language. In the 2.x line from 2.8.0.0 until 2.19.6.0, and the 3.x line prior to 3.7.0.0, a remote authenticated user with basic read/search permissions can provide a crafted `cursor` parameter to the `plugins/sql` endpoint and trigger unsafe deserialization of untrusted data, resulting in arbitrary code execution on the server. This issue is fixed in repository releases 2.19.6.0 and 3.7.0.0. | |
| Title | OpenSearch SQL plugin: Unsafe cursor deserialization permits server code execution | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV4_0
|