What is CVE-2019-3802?

CVE-2019-3802 is a medium-severity security vulnerability in org.springframework.data:spring-data-jpa (maven), affecting versions < 1.11.22. It is fixed in 1.11.22, 2.1.8.

How severe is CVE-2019-3802?

CVE-2019-3802 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.springframework.data:spring-data-jpa are affected by CVE-2019-3802?

org.springframework.data:spring-data-jpa (maven) versions < 1.11.22 is affected.

Is there a fix for CVE-2019-3802?

Yes. CVE-2019-3802 is fixed in 1.11.22, 2.1.8. Upgrade to this version or later.

Is CVE-2019-3802 exploitable, and should I be worried?

Whether CVE-2019-3802 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-3802 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-3802

Q: How severe is CVE-2019-3802?

CVE-2019-3802 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.springframework.data:spring-data-jpa are affected by CVE-2019-3802?

org.springframework.data:spring-data-jpa (maven) versions < 1.11.22 is affected.

Q: Is there a fix for CVE-2019-3802?

Yes. CVE-2019-3802 is fixed in 1.11.22, 2.1.8. Upgrade to this version or later.

Q: Is CVE-2019-3802 exploitable, and should I be worried?

Whether CVE-2019-3802 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-3802 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-3802?

Upgrade: org.springframework.data:spring-data-jpa to 1.11.22 or later, org.springframework.data:spring-data-jpa to 2.1.8 or later, org.springframework.data:spring-data-jpa to 2.1.8 or later.

Summary

Improper Neutralization of Wildcards or Matching Symbols

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.

Impact

CVE-2019-3802 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.22, 2.1.8); upgrading removes the vulnerable code path.

Affected versions

org.springframework.data:spring-data-jpa (< 1.11.22) org.springframework.data:spring-data-jpa (>= 2.1.0, < 2.1.8) org.springframework.data:spring-data-jpa (>= 2.0.0, <= 2.0.14)

Security releases

org.springframework.data:spring-data-jpa → 1.11.22 (maven) org.springframework.data:spring-data-jpa → 2.1.8 (maven) org.springframework.data:spring-data-jpa → 2.1.8 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.springframework.data:spring-data-jpa to 1.11.22 or later; org.springframework.data:spring-data-jpa to 2.1.8 or later; org.springframework.data:spring-data-jpa to 2.1.8 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-3802? CVE-2019-3802 is a medium-severity security vulnerability in org.springframework.data:spring-data-jpa (maven), affecting versions < 1.11.22. It is fixed in 1.11.22, 2.1.8.
How severe is CVE-2019-3802? CVE-2019-3802 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.springframework.data:spring-data-jpa are affected by CVE-2019-3802? org.springframework.data:spring-data-jpa (maven) versions < 1.11.22 is affected.
Is there a fix for CVE-2019-3802? Yes. CVE-2019-3802 is fixed in 1.11.22, 2.1.8. Upgrade to this version or later.
Is CVE-2019-3802 exploitable, and should I be worried? Whether CVE-2019-3802 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-3802 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-3802?
- Upgrade org.springframework.data:spring-data-jpa to 1.11.22 or later
- Upgrade org.springframework.data:spring-data-jpa to 2.1.8 or later
- Upgrade org.springframework.data:spring-data-jpa to 2.1.8 or later

Other vulnerabilities in org.springframework.data:spring-data-jpa

CVE-IDSeverityPackage summary

CVE-2016-6652Mediumorg.springframework.data:spring-data-jpa: Improper Neutralization of Special Elements used in an SQL Command Pivotal Spring Data JPA CVE-2019-3797Mediumorg.springframework.data:spring-data-jpa: Exposure of Sensitive Information to an Unauthorized Actor and SQL Injection in Spring Data JPA