Security readout for executives and security teams
Plain-English summary
This is a low-severity information exposure issue in Spring Data JPA query-by-example matching. If an application lets a logged-in user influence certain string matchers, a crafted value could make searches return more records than intended.
Executive priority
Treat as a targeted remediation item, not an emergency. Prioritize applications where search results include customer, account, or sensitive operational data.
Technical view
Spring Data JPA versions up to 2.1.6, 2.0.14, and 1.11.20 can overmatch when ExampleMatcher uses STARTING, ENDING, or CONTAINING with a malicious example value. The impact is limited to confidentiality; integrity and availability are not indicated.
Likely exposure
Exposure is most likely in Java applications using Spring Data JPA query-by-example search where user-supplied values reach affected ExampleMatcher string modes.
Exploitation context
The CVSS vector requires network access, low complexity, low privileges, and user interaction. The provided sources do not indicate public exploitation or CISA KEV listing.
Researcher notes
Evidence supports additional result disclosure through crafted example values, but the bundle does not provide exploit details, fixed release numbers, or observed exploitation. Validate exposure through dependency and code-path review.
Mitigation direction
- Identify applications using affected Spring Data JPA versions.
- Check Spring/Pivotal advisory for supported fixed versions and upgrade guidance.
- Review user-facing search features using STARTING, ENDING, or CONTAINING matchers.
- Limit sensitive data exposure from affected search results until remediated.
Validation and detection
- Inventory dependency versions for Spring Data JPA across applications.
- Search code for ExampleMatcher.StringMatcher.STARTING, ENDING, and CONTAINING usage.
- Confirm whether user-controlled values reach those matchers.
- Regression-test affected search paths for excessive result disclosure.
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-155: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-3802 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-3802CVE 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 Wildcards or Matching Symbols
Improper Neutralization of Wildcards or Matching Symbols represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.