First published: Mon Apr 08 2019(Updated: )
This affects Spring Data JPA in versions up to and including 2.1.5, 2.0.13 and 1.11.19. Derived queries using any of the predicates ‘startingWith’, ‘endingWith’ or ‘containing’ could return more results than anticipated when a maliciously crafted query parameter value is supplied. Also, LIKE expressions in manually defined queries could return unexpected results if the parameter values bound did not have escaped reserved characters properly.
Credit: security_alert@emc.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pivotal Software Spring Data Java Persistence Api | >=1.11.0<=1.11.19 | |
Pivotal Software Spring Data Java Persistence Api | >=2.0.0<=2.0.13 | |
Pivotal Software Spring Data Java Persistence Api | >=2.1.0<=2.1.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-3797 is a vulnerability affecting Spring Data JPA versions up to and including 2.1.5, 2.0.13, and 1.11.19.
The severity of CVE-2019-3797 is medium with a severity value of 5.3.
CVE-2019-3797 affects Spring Data JPA by allowing derived queries using 'startingWith', 'endingWith', or 'containing' predicates to return more results than expected when a malicious query parameter value is used.
Spring Data JPA versions up to and including 2.1.5, 2.0.13, and 1.11.19 are affected by CVE-2019-3797.
To fix CVE-2019-3797, upgrade to Spring Data JPA version 2.1.6, 2.0.14, or 1.11.20, depending on the version you are using.