Skip to content
Fencer Intel
medium 5.9

GHSA-3xgr-h5hq-7299 json

GeoIP processor disables SSL certificate validation when downloading databases

published last yr. modified last yr.

cvss
5.9
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

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.

### Patches

Data Prepper 2.12.2 contains a fix for this issue.

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

Patch / fix

  • maven org.opensearch.dataprepper.plugins:geoip-processor 2.12.2

Is GHSA-3xgr-h5hq-7299 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.opensearch.dataprepper.plugins:geoip-processor
>=2.7.0, <2.12.2
2.12.2

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.