CVE-2019-3802GHSA-XGGX-FX6W-V7CH
Additional information exposure with Spring Data JPA example matcher
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.8.RELEASE, 1.11.22.RELEASE, 2.1.8, 1.11.22
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Spring Spring Data JPA
From 2.1 · fixed in 2.1.8.RELEASE; From 1.11 · fixed in 1.11.22.RELEASE
- org.springframework.data:spring-data-jpaMaven
From 2.1.0 · fixed in 2.1.8
- org.springframework.data:spring-data-jpaMaven
From 2.0.0 · fixed in 2.1.8
- org.springframework.data:spring-data-jpaMaven
fixed in 1.11.22