WaratekVRT Sign in

CVE-2020-5411 Spring Batch

Affected softwareSpring Batch
Severity8.1 High CVSS 3.1 2 scores
Fixed in4.2.3
WeaknessDeserialization of untrusted data (CWE-502)
Published11 Jun 2020
Updated1 Sep 2026

Description

When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to arbitrary code execution. Jackson fixed this vulnerability by blacklisting known "deserialization gadgets". Spring Batch configures Jackson with global default typing enabled which means that through the previous exploit, arbitrary code could be executed if all of the following is true: * Spring Batch's Jackson support is being leveraged to serialize a job's ExecutionContext. * A malicious user gains write access to the data store used by the JobRepository (where the data to be deserialized is stored). In order to protect against this type of attack, Jackson prevents a set of untrusted gadget classes from being deserialized. Spring Batch should be proactive against blocking unknown "deserialization gadgets" when enabling default typing.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 6 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS 1.7% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

CVSS

8.1 HIGH v3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 8.1 HIGH CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H NVD Primary published
CVSS 2.0 6.8 none AV:N/AC:M/Au:N/C:P/I:P/A:P NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.springframework.batch:spring-batch-core 4.0.0 4.2.3 unbounded

Products and versions

2 products, 4 version entries
SourceVendorProductSchemeAffected versions
nvd broadcom spring batch generic ≥ 4.0.0 and ≤ 4.0.4 · ≥ 4.1.0 and ≤ 4.1.4 · ≥ 4.2.0 and ≤ 4.2.2
osv org.springframework.batch spring-batch-core generic ≥ 4.0.0 and < 4.2.3

References

URLTags
https://github.com/spring-projects/spring-batch PACKAGE
https://tanzu.vmware.com/security/cve-2020-5411 WEB

Timeline

Published2020-06-11By the CVE Program.
NVD record modified2026-09-01NVD's own last-modified date for this record.