CVE-2019-3797 — spring-data-jpa
MEDIUMCVE-2019-3797 is a medium-severity (CVSS 5.3) SQL Injection vulnerability in org.springframework.data:spring-data-jpa. A fix is available for org.springframework.data:spring-data-jpa — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor and SQL Injection in Spring Data JPA
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.data:spring-data-jpa☕org.springframework.data:spring-data-jpa☕org.springframework.data:spring-data-jpaReal-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.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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-jpa | all versions | 1.11.20org.springframework.data:spring-data-jpa:1.11.20 |
| ☕Maven | org.springframework.data:spring-data-jpa | ≥ 2.0.0&&< 2.0.14 | 2.0.14org.springframework.data:spring-data-jpa:2.0.14 |
| ☕Maven | org.springframework.data:spring-data-jpa | ≥ 2.1.0&&< 2.1.6 | 2.1.6org.springframework.data:spring-data-jpa:2.1.6 |
Affected Products
spring data java persistence apipivotal_softwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-jpa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.data:spring-data-jpa to 1.11.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3797 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Fuse 7.7.0 | spring-data-jpa | RHSA-2020:3192 |
Frequently Asked Questions
Is CVE-2019-3797 in your dependencies?
Find it across Maven, including transitive dependencies.