GHSA-3XGR-H5HQ-7299

Workarounds

If upgrading is not immediately possible:

• Use local GeoIP database files instead of downloading from HTTP URLs
• Ensure database downloads occur only over trusted networks

The GeoIP processor in Data Prepper was configured to trust all SSL certificates and disable hostname verification when downloading GeoIP databases from HTTP URLs, making downloads vulnerable to man-in-the-middle attacks.

The GeoIP processor included a custom SSL implementation that completely bypassed certificate validation when downloading GeoIP databases from external sources. The initiateSSL() method incorrectly implemented an approach for trusting all certificates. Specifically it:

• Accepted all SSL certificates without validation
• Disabled server certificate verification
• Disabled client certificate verification
• Disabled hostname verification

This configuration made database downloads vulnerable to man-in-the-middle attacks, potentially allowing attackers to serve malicious GeoIP databases that could compromise the integrity of geolocation data processing.

GHSA-3XGR-H5HQ-7299 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.12.2); upgrading removes the vulnerable code path.

Kodem intelligence

Data Prepper 2.12.2 contains a fix for this issue.

1. What is GHSA-3XGR-H5HQ-7299? GHSA-3XGR-H5HQ-7299 is a medium-severity security vulnerability in org.opensearch.dataprepper.plugins:geoip-processor (maven), affecting versions >= 2.7.0, < 2.12.2. It is fixed in 2.12.2.
2. How severe is GHSA-3XGR-H5HQ-7299? GHSA-3XGR-H5HQ-7299 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.opensearch.dataprepper.plugins:geoip-processor are affected by GHSA-3XGR-H5HQ-7299? org.opensearch.dataprepper.plugins:geoip-processor (maven) versions >= 2.7.0, < 2.12.2 is affected.
4. Is there a fix for GHSA-3XGR-H5HQ-7299? Yes. GHSA-3XGR-H5HQ-7299 is fixed in 2.12.2. Upgrade to this version or later.
5. Is GHSA-3XGR-H5HQ-7299 exploitable, and should I be worried? Whether GHSA-3XGR-H5HQ-7299 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-3XGR-H5HQ-7299 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-3XGR-H5HQ-7299? Upgrade org.opensearch.dataprepper.plugins:geoip-processor to 2.12.2 or later.