Most recent entries from all

EUVD-2026-255170

2026-10-06T07:00:12.210366+00:00

EUVD-2026-255170

fkie_cve-2025-62371

2026-10-06T07:00:12.210402+00:00

OpenSearch Data Prepper as an open source data collector for observability data. In versions prior to 2.12.2, the OpenSearch sink and source plugins in Data Prepper trust all SSL certificates by default when no certificate path is provided. Prior to this fix, the OpenSearch sink and source plugins would automatically use a trust all SSL strategy when connecting to OpenSearch clusters if no certificate path was explicitly configured. This behavior bypasses SSL certificate validation, potentially allowing attackers to intercept and modify data in transit through man-in-the-middle attacks. The vulnerability affects connections to OpenSearch when the cert parameter is not explicitly provided. This issue has been patched in version 2.12.2. As a workaround, users can add the cert parameter to their OpenSearch sink or source configuration with the path to the cluster's CA certificate.

GHSA-43ff-rr26-8hx4 — OpenSearch Data Prepper plugins trust all SSL certificates by default

2026-10-06T07:00:12.210440+00:00

Affected: Maven: org.opensearch.dataprepper.plugins:opensearch

### Impact

The OpenSearch sink and source plugins in Data Prepper are configured to trust all SSL certificates by default when no certificate path was provided, making connections vulnerable to man-in-the-middle attacks.

Prior to this fix, the OpenSearch sink and source plugins would automatically use a trust all SSL strategy when connecting to OpenSearch clusters if no certificate path was explicitly configured. This behavior bypassed SSL certificate validation, potentially allowing attackers to intercept and modify data in transit through man-in-the-middle attacks.

The vulnerability affects connections to OpenSearch when the `cert` parameter is not explicitly provided.

### Patches

Data Prepper 2.12.2

### Workarounds

If you cannot immediately upgrade to the fixed version, you can implement the following workaround.

#### OpenSearch sink

Add the `cert` parameter to your OpenSearch sink configuration with the path to your cluster's CA certificate. The following example shows how to accomplish this.

``` sink: - opensearch: hosts: ["https://your-opensearch-cluster:9200"] cert: /path/to/your/ca-certificate.pem ```

#### OpenSearch source

Add the `cert` parameter to your OpenSearch sink configuration with the path to your cluster's CA certificate. The following example shows how to accomplish this.

``` sink: - opensearch: hosts: ["https://your-opensearch-cluster:9200"] connection: cert: /path/to/your/ca-certificate.pem ```

### Refe…