Skip to content

OpenSearch Data Prepper uses deprecated SSL protocol identifier

Moderate severity GitHub Reviewed Published Oct 15, 2025 in opensearch-project/data-prepper • Updated Oct 15, 2025

Package

maven org.opensearch.dataprepper.plugins:geoip-processor (Maven)

Affected versions

>= 2.4.0, < 2.12.2

Patched versions

2.12.2

Description

Impact

The GeoIP processor and Kafka source and buffer were using the deprecated "SSL" protocol identifier when creating SSL contexts, potentially allowing the use of insecure SSL protocols instead of modern TLS versions.

Multiple Data Prepper plugins used SSLContext.getInstance("SSL") which could potentially allow the use of deprecated SSL protocols (SSLv2, SSLv3) that have known security vulnerabilities. While modern Java implementations typically default to secure TLS versions even with the "SSL" identifier, explicitly using "TLS" ensures that only secure TLS protocols are negotiated.

The affected components were:

  • GeoIP Processor: The DBSource.initiateSSL() method used for downloading GeoIP databases from external sources

  • Kafka Plugin: Both CustomClientSslEngineFactory and InsecureSslEngineFactory classes used for Kafka client connections

This could potentially allow connections to negotiate weaker SSL protocols instead of enforcing modern TLS versions, reducing the security of data transmission.

Patches

Data Prepper 2.12.2 contains a fix for this issue.

Workarounds

If upgrading is not immediately possible:

  1. Ensure your Java runtime is configured to disable deprecated SSL protocols
  2. Use network-level controls to enforce TLS-only connections
  3. Use external tools to verify that deprecated SSL protocols are not allowed.

References

@cwperks cwperks published to opensearch-project/data-prepper Oct 15, 2025
Published to the GitHub Advisory Database Oct 15, 2025
Reviewed Oct 15, 2025
Last updated Oct 15, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

Weaknesses

Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-28gg-8qqj-fhh5

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.