Spring Data JPA up to 1.11.19/2.0.13/2.1.5 Derived Query information disclosure

Summaryinfo

A vulnerability labeled as problematic has been found in Spring Data JPA up to 1.11.19/2.0.13/2.1.5. This impacts an unknown function of the component Derived Query Handler. Such manipulation leads to information disclosure. This vulnerability is documented as CVE-2019-3797. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Spring Data JPA up to 1.11.19/2.0.13/2.1.5. It has been rated as problematic. Affected by this issue is an unknown part of the component Derived Query Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:

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.

The bug was discovered 01/03/2019. The weakness was released 05/06/2019 (Website). The advisory is shared for download at pivotal.io. This vulnerability is handled as CVE-2019-3797 since 01/03/2019. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

The vulnerability was handled as a non-public zero-day exploit for at least 123 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Spring Data JPA

Version

• 1.11.0
• 1.11.1
• 1.11.2
• 1.11.3
• 1.11.4
• 1.11.5
• 1.11.6
• 1.11.7
• 1.11.8
• 1.11.9
• 1.11.10
• 1.11.11
• 1.11.12
• 1.11.13
• 1.11.14
• 1.11.15
• 1.11.16
• 1.11.17
• 1.11.18
• 1.11.19
• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion