Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-xggx-fx6w-v7ch

MEDIUM

Improper Neutralization of Wildcards or Matching Symbols

Also known asCVE-2019-3802
Published
Jun 4, 2019
Updated
Nov 8, 2023
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
org.springframework.data:spring-data-jpaorg.springframework.data:spring-data-jpaorg.springframework.data:spring-data-jpa

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

This affects Spring Data JPA in versions up to and including 2.1.6, 2.0.14 and 1.11.20. ExampleMatcher using ExampleMatcher.StringMatcher.STARTING, ExampleMatcher.StringMatcher.ENDING or ExampleMatcher.StringMatcher.CONTAINING could return more results than anticipated when a maliciously crafted example value is supplied.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework.data:spring-data-jpa2.1.0&&< 2.1.82.1.8
Mavenorg.springframework.data:spring-data-jpa2.0.0&&< 2.1.82.1.8
Mavenorg.springframework.data:spring-data-jpaall versions1.11.22

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-jpa. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.springframework.data:spring-data-jpa to 2.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xggx-fx6w-v7ch is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-xggx-fx6w-v7ch is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xggx-fx6w-v7ch. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects Spring Data JPA in versions up to and including 2.1.6, 2.0.14 and 1.11.20. ExampleMatcher using ExampleMatcher.StringMatcher.STARTING, ExampleMatcher.StringMatcher.ENDING or ExampleMatcher.StringMatcher.CONTAINING could return more results than anticipated when a maliciously crafted example value is supplied.
O3 Security · Impact-Aware SCA

Is GHSA-xggx-fx6w-v7ch in your dependencies?

O3 detects GHSA-xggx-fx6w-v7ch across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.