GHSA-28gg-8qqj-fhh5
OpenSearch Data Prepper uses deprecated SSL protocol identifier
GHSA-28gg-8qqj-fhh5 is a medium vulnerability (CVSS 4.8) in org.opensearch.dataprepper.plugins:geoip-processor, published October 15, 2025. No source lists public exploit code. Fixed in org.opensearch.dataprepper.plugins:geoip-processor 2.12.2.
- Severity
- 4.8 MediumCVSS 3.1, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
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 sourcesKafka Plugin: Both
CustomClientSslEngineFactoryandInsecureSslEngineFactoryclasses 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:
- Ensure your Java runtime is configured to disable deprecated SSL protocols
- Use network-level controls to enforce TLS-only connections
- Use external tools to verify that deprecated SSL protocols are not allowed.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.opensearch.dataprepper.plugins:geoip-processorMaven | 2.4.0 up to 2.12.2 | 2.12.2 |
org.opensearch.dataprepper.plugins:geoip-processorMaven | 2.4.0 up to 2.12.2, plus listed versions 2.12.02.12.1 | 2.12.2 |
What each source reports
GitHub Advisories Score used
OpenSearch Data Prepper uses deprecated SSL protocol identifier
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 sourcesKafka Plugin: Both
CustomClientSslEngineFactoryandInsecureSslEngineFactoryclasses 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:
- Ensure your Java runtime is configured to disable deprecated SSL protocols
- Use network-level controls to enforce TLS-only connections
- Use external tools to verify that deprecated SSL protocols are not allowed.
- Record
GHSA-28gg-8qqj-fhh5- CVSS 3.1
- 4.8 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N - Weakness
- CWE-295
- Updated
- 2026-11-02
OSV
OpenSearch Data Prepper uses deprecated SSL protocol identifier
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 sourcesKafka Plugin: Both
CustomClientSslEngineFactoryandInsecureSslEngineFactoryclasses 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:
- Ensure your Java runtime is configured to disable deprecated SSL protocols
- Use network-level controls to enforce TLS-only connections
- Use external tools to verify that deprecated SSL protocols are not allowed.
- Record
GHSA-28gg-8qqj-fhh5- CVSS 3.1
- 4.8 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N - Weakness
- CWE-295
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.