CVE-2019-3802

CVE-2019-3802 is a medium-severity vulnerability in Pivotal Software Spring Data Java Persistance Api with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-155.

Key facts

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.

Frequently asked questions

What is CVE-2019-3802?
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.
How severe is CVE-2019-3802?
CVE-2019-3802 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2019-3802 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-3802?
CVE-2019-3802 affects Pivotal Software Spring Data Java Persistance Api. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-3802?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-3802 published?
CVE-2019-3802 was published on 2019-06-03 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-155 vulnerabilities

Browse all CWE-155 vulnerabilities →