# CVE-2020-5411: Jackson Configuration Allows Code Execution with Unknown "Serialization Gadgets"

> Attackers with write access to the job repository can execute arbitrary code via unsafe Jackson deserialization in Spring Batch.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4ph4-q9r5-6wm6

## What is CVE-2020-5411?

CVE-2020-5411 is a high-severity unsafe deserialization vulnerability in Spring Batch, published on 11 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2020-5411?

2 open source packages ship an affected version, including org.springframework.batch:spring-batch-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.batch:spring-batch-core` | Maven | From 4.0.0 | 4.2.3 |
| `org.springframework.batch:spring-batch-core` | Maven | From 4.0.0 | 4.2.3 |

Products: Broadcom Spring Batch.

## How do I fix CVE-2020-5411?

Upgrade org.springframework.batch:spring-batch-core to 4.2.3 or later.

## Is CVE-2020-5411 being exploited?

There is no known exploitation of CVE-2020-5411 in the wild and no public exploit code.

## Other vulnerabilities in Spring Batch

- [CVE-2019-3774](https://insights.sbomify.com/CVE-2019-3774/): Spring Batch XML External Entity Injection (XXE) (critical 9.8)
- [CVE-2026-47881](https://insights.sbomify.com/CVE-2026-47881/): Denial of Service in Spring Batch FlatFileItemReader via Malformed Input File (medium 5.9)
- [CVE-2026-47875](https://insights.sbomify.com/CVE-2026-47875/): JobParameterDeserializer bypasses the trusted-type allowlist (medium 5.6)
- [CVE-2026-47878](https://insights.sbomify.com/CVE-2026-47878/): Unsafe Java deserialization in DefaultExecutionContextSerializer without class allowlist (medium 5.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5411 and fix it if it is affected.

What it is: CVE-2020-5411 is a high-severity unsafe deserialization vulnerability in Spring Batch, published on 11 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-5411 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.batch:spring-batch-core (Maven): affected from 4.0.0; fixed in 4.2.3
- org.springframework.batch:spring-batch-core (Maven): affected from 4.0.0; fixed in 4.2.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-5411/ (Markdown: https://insights.sbomify.com/CVE-2020-5411/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5411
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5411
- OSV: https://osv.dev/vulnerability/CVE-2020-5411

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-5411/
Summaries are generated and may contain mistakes; the official description above is the record.