How severe is GHSA-28gg-8qqj-fhh5?

GHSA-28gg-8qqj-fhh5 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-28gg-8qqj-fhh5?

GHSA-28gg-8qqj-fhh5 affects the following packages: org.opensearch.dataprepper.plugins:geoip-processor (Maven). Ecosystems affected: Maven.

How do I fix GHSA-28gg-8qqj-fhh5?

Update org.opensearch.dataprepper.plugins:geoip-processor to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-28gg-8qqj-fhh5 is resolved across your whole dependency graph.

How do I detect GHSA-28gg-8qqj-fhh5 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch.dataprepper.plugins:geoip-processor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-28gg-8qqj-fhh5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-28gg-8qqj-fhh5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-28gg-8qqj-fhh5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-28gg-8qqj-fhh5 published, and has it been updated?

GHSA-28gg-8qqj-fhh5 was published on October 15, 2025 and was last updated on October 16, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

OpenSearch Data Prepper uses deprecated SSL protocol identifierGHSA-28gg-8qqj-fhh5

MEDIUMFix: opensearch-project/data-prepper@fa21a60

GHSA-28gg-8qqj-fhh5 is a medium-severity (CVSS 4.8) vulnerability in org.opensearch.dataprepper.plugins:geoip-processor. A fix is available for org.opensearch.dataprepper.plugins:geoip-processor — see the affected versions and patch details below.

Published

Oct 15, 2025

Updated

Oct 16, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 16, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕org.opensearch.dataprepper.plugins:geoip-processor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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:

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opensearch.dataprepper.plugins:geoip-processor`	≥ 2.4.0&&< 2.12.2	2.12.2`org.opensearch.dataprepper.plugins:geoip-processor:2.12.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch.dataprepper.plugins:geoip-processor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opensearch.dataprepper.plugins:geoip-processor to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-28gg-8qqj-fhh5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 negotiate

O3 Security · Impact-Aware SCA

Is GHSA-28gg-8qqj-fhh5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works