Skip to content
Fencer Intel
low 3.5

CVE-2019-3802 json

Additional information exposure with Spring Data JPA example matcher

published 7y ago modified 4mo ago also GHSA-xggx-fx6w-v7ch , EUVD-2019-0572

cvss
3.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.data:spring-data-jpa 1.11.22, 2.1.8
  • Spring Spring Data JPA 1.11.22.RELEASE, 2.1.8.RELEASE

Is CVE-2019-3802 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-3802 updated cvss 5.3

spring-data-api: potential information disclosure through maliciously crafted example value in ExampleMatcher

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 3.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.data:spring-data-jpa
>=2.1.0, <2.1.8
>=2.0.0, <2.1.8
<1.11.22
2.1.8
1.11.22

Affected products

  • Spring Spring Data JPA

Classification

Weakness
  • CWE-155 Improper Neutralization of Wildcards or Matching Symbols
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.