Menu

Star on GitHub · 3.2k

CVE-2019-3797

3.5 · LOW

This affects Spring Data JPA in versions up to and including 2.1.5, 2.0.13 and 1.11.19.

Published May 6, 2019CWE-89EPSS 1.09%

Overview

CVE-2019-3797 is a low-severity vulnerability. It was published on May 6, 2019 and has a CVSS 3.0 base score of 3.5 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.5, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

This affects Spring Data JPA in versions up to and including 2.1.5, 2.0.13 and 1.11.19. Derived queries using any of the predicates ‘startingWith’, ‘endingWith’ or ‘containing’ could return more results than anticipated when a maliciously crafted query parameter value is supplied. Also, LIKE expressions in manually defined queries could return unexpected results if the parameter values bound did not have escaped reserved characters properly.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2019-3797?

CVE-2019-3797 is a low-severity vulnerability. It was published on May 6, 2019 and has a CVSS 3.0 base score of 3.5 (LOW).

How severe is CVE-2019-3797?

This vulnerability has a CVSS 3.0 base score of 3.5, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2019-3797?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2019-3797?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2019-3797 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2019

View all