Spring Batch up to 3.0.9/4.0.1/4.1.0 XML Data xml external entity reference

Summaryinfo

A vulnerability identified as critical has been detected in Spring Batch up to 3.0.9/4.0.1/4.1.0. The affected element is an unknown function of the component XML Data Handler. The manipulation leads to xml external entity reference. This vulnerability is documented as CVE-2019-3774. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Spring Batch up to 3.0.9/4.0.1/4.1.0. This issue affects some unknown functionality of the component XML Data Handler. The manipulation with an unknown input leads to a xml external entity reference vulnerability. Using CWE to declare the problem leads to CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Spring Batch versions 3.0.9, 4.0.1, 4.1.0, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.

The bug was discovered 01/14/2019. The weakness was released 01/18/2019 (Website). It is possible to read the advisory at pivotal.io. The identification of this vulnerability is CVE-2019-3774 since 01/03/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 4 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Spring Batch

Version

• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4
• 3.0.5
• 3.0.6
• 3.0.7
• 3.0.8
• 3.0.9
• 4.0
• 4.0.0
• 4.0.1
• 4.1.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion