CVE-2019-3797 json
Additional information exposure with Spring Data JPA derived queries
published 7y ago modified 4mo ago also GHSA-jgmr-wrwx-mgfj , EUVD-2019-0471
- cvss
- 3.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.data:spring-data-jpa 1.11.20, 2.0.14, 2.1.6
- Spring Spring Boot v1.5.20.RELEASE, v2.0.9.RELEASE, v2.1.4.RELEASE
Is CVE-2019-3797 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-3797 updated cvss 3.7
spring-data-jpa: Additional information exposure with Spring Data JPA derived queries
-
Red Hat Fuse 7.7.0fixed: vendor fix RHSA-2020:3192
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 3.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N |
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.data:spring-data-jpa | <1.11.20 >=2.0.0, <2.0.14 >=2.1.0, <2.1.6 |
1.11.20 2.0.14 2.1.6 |
Affected products
- Spring Spring Boot
Classification
- Weakness
- Technology feeds
References
-
pivotal.io
/security/cve-2019-3797
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-3797
advisory
Sources
- CVE List CVE-2019-3797
- GitHub Advisory GHSA-jgmr-wrwx-mgfj
- NVD CVE-2019-3797
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.