CVE-2019-3797: Additional information exposure with Spring Data JPA derived queries

Published Apr 8, 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.

Affected Software

6 affected componentsFixes available
redhat/spring-data-jpa<2.1.6
2.1.6
redhat/spring-data-jpa<2.0.14
2.0.14
redhat/spring-data-jpa<1.11.20
1.11.20
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

Event History

Apr 8, 2019
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·07:11 PM
DescriptionSeverityAffected Software
May 6, 2019
CVE Published
via MITRE·03:21 PM
Data Sourced
via MITRE·03:21 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2019-3797?

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.

2

What is the severity of CVE-2019-3797?

The severity of CVE-2019-3797 is medium with a severity value of 5.3.

3

How does CVE-2019-3797 affect Spring Data JPA?

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.

4

Which software versions are affected by CVE-2019-3797?

Spring Data JPA versions up to and including 2.1.5, 2.0.13, and 1.11.19 are affected by CVE-2019-3797.

5

How can I fix 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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203