CVE-2019-3802

Additional information exposure with Spring Data JPA example matcher

Description

This affects Spring Data JPA in versions up to and including 2.1.6, 2.0.14 and 1.11.20. ExampleMatcher using ExampleMatcher.StringMatcher.STARTING, ExampleMatcher.StringMatcher.ENDING or ExampleMatcher.StringMatcher.CONTAINING could return more results than anticipated when a maliciously crafted example value is supplied.

Category

5.3
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.24%
Vendor Advisory pivotal.io
Affected: Spring Spring Data JPA
Published at:
Updated at:

References

Link Tags
https://pivotal.io/security/cve-2019-3802 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2019-3802?
CVE-2019-3802 has been scored as a medium severity vulnerability.
How to fix CVE-2019-3802?
To fix CVE-2019-3802, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-3802 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2019-3802 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2019-3802?
CVE-2019-3802 affects Spring Spring Data JPA.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.