Security readout for executives and security teams
Plain-English summary
CVE-2019-3797 is a low-severity information exposure issue in affected Spring Data JPA query handling. In specific query patterns, a crafted parameter could make an application return more records than intended. Business urgency depends on whether affected query features protect sensitive data behind authenticated user flows.
Executive priority
Treat this as a targeted backlog security fix unless affected searches expose regulated, customer, or internal confidential data. Prioritize faster where search endpoints cross tenant, account, or role boundaries.
Technical view
Spring Data JPA versions up to 2.1.5, 2.0.13, and 1.11.19 are affected. Derived queries using startingWith, endingWith, or containing, and manually defined LIKE expressions without proper reserved-character escaping, may return unexpected extra results. The CVSS vector indicates network reachability, low complexity, required privileges, user interaction, and low confidentiality impact.
Likely exposure
Exposure is most likely in Spring Boot or Spring Data JPA applications using affected versions and repository queries with the named predicates or manual LIKE expressions over sensitive records.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked KEV. The issue requires a maliciously crafted query parameter and conditions where affected query methods influence returned data.
Researcher notes
The CVE maps to CWE-89, but the described impact is overbroad query matching and information exposure, not confirmed command execution. Source details do not provide exact fixed versions or exploit evidence, so remediation should follow vendor advisory guidance.
Mitigation direction
- Inventory Spring Boot and Spring Data JPA versions.
- Check Spring or Pivotal guidance for fixed releases.
- Upgrade affected Spring Data JPA dependencies per vendor guidance.
- Review manual LIKE queries for proper reserved-character escaping.
- Limit query results to authorized records server-side.
Validation and detection
- Confirm dependency versions against the affected version ranges.
- Identify repository methods using startingWith, endingWith, or containing.
- Review manually defined LIKE expressions using user-controlled parameters.
- Test affected search paths for unexpected overbroad results.
- Verify authorization filters still apply after query expansion.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-3797 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.5 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N2.11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
3.5LowVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://pivotal.io/security/cve-2019-3797CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.