CVE-2019-3797: Exposure of Sensitive Information to an Unauthorized Actor and SQL Injection in Spring Data JPA

CVE-2019-3797 · Severity: low · CVSS 3 · Published 2019-05-14

Exposure of Sensitive Information to an Unauthorized Actor and SQL Injection in Spring Data JPA

Technologies: org.springframework.data:spring-data-jpa (Maven). Vendors: Maven.

Quick answers

Is CVE-2019-3797 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-3797 being exploited in the wild.
How severe is CVE-2019-3797?
Low severity, with a CVSS score of 3, published 14 May 2019.
Which products and versions are affected?
org.springframework.data:spring-data-jpa (Maven) ECOSYSTEM:introduced=0,fixed=1.11.20.
Is there a fix for CVE-2019-3797?
Yes. org.springframework.data:spring-data-jpa (Maven): upgrade to 1.11.20 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-3797?
Check whether you run org.springframework.data:spring-data-jpa (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.data:spring-data-jpa (Maven): upgrade to 1.11.20 or later
    # set org.springframework.data:spring-data-jpa to 1.11.20 in your pom.xml or build.gradle

Affected products

  • org.springframework.data:spring-data-jpa (Maven) ECOSYSTEM:introduced=0,fixed=1.11.20

Identifiers

  • CVE-2019-3797
  • GHSA-jgmr-wrwx-mgfj

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.