cve.bz

CVE-2019-3797 pivotal software spring data java persistence api: SQL Injection

5.3 mediumEPSS 1.1%Fix available

Medium (5.3) in pivotal software spring data java persistence api. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.data:spring-data-jpa 1.11.20, 2.0.14, 2.1.6.

On this page
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.

Severity

CVSS 3.0

5.3 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 66th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-3797 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-3797?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-3797?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-3797 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Bootfrom 2.0 before v2.0.9.RELEASE
Spring Bootfrom 1.5 before v1.5.20.RELEASE
Spring Bootfrom 2.1 before v2.1.4.RELEASE

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jgmr-wrwx-mgfjMavenorg.springframework.data:spring-data-jpa<1.11.201.11.20
GHSA-jgmr-wrwx-mgfjMavenorg.springframework.data:spring-data-jpa>=2.0.0 <2.0.142.0.14
GHSA-jgmr-wrwx-mgfjMavenorg.springframework.data:spring-data-jpa>=2.1.0 <2.1.62.1.6

Red Hat

Red Hat rates this Low.

ProductPackageStateAdvisory
Red Hat Fuse 7.7.0spring-data-jpaFixed 2020-07-28RHSA-2020:3192

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-3797.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON