Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-5411: When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to

53
This month
HIGH 8.1REMOTEUPGRADE

CVE-2020-5411 is a high-severity flaw (CVSS 8.1) affecting spring batch. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance1.7% (top 23%)
CISA exploited listNo
WeaknessCWE-502
Published2020-06-11
Last modified2026-09-01
Publisher (CNA): Pivotal Software, Inc. · Vendor: broadcom

Share: LinkedIn · X · Reddit

Last updated 2026-09-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

broadcom spring batch UPGRADE
Affected: >= 4.0.0 and <= 4.0.4 · >= 4.1.0 and <= 4.1.4 · >= 4.2.0 and <= 4.2.2
Fixed in: newer than 4.2.2
Safe to downgrade to: a release before 4.0.0
1. Check installed version
apt-cache policy spring-batch || rpm -q spring-batch || spring-batch --version
2. UPGRADE to newer than 4.2.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-batch
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-batch
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)
apt-cache madison spring-batch sudo apt install spring-batch=<VERSION_BEFORE_4.0.0> sudo apt-mark hold spring-batch
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-batch sudo dnf downgrade spring-batch-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add spring-batch
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5411?

spring batch: upgrade to newer than 4.2.2. Exact commands for each OS are on this page.

Is CVE-2020-5411 being exploited?

CVE-2020-5411 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5411 affect?

CVE-2020-5411 affects spring batch. Severity is high (CVSS 8.1). 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 configur

How urgent is CVE-2020-5411?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.