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

Published Jun 11, 2020
·
Updated

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.

Affected Software

6 affected components
Pivotal Software Spring Batch>=4.0.0<=4.0.4
Pivotal Software Spring Batch>=4.1.0<=4.1.4
Pivotal Software Spring Batch>=4.2.0<=4.2.2
Broadcom Spring Batch>=4.0.0<=4.0.4
Broadcom Spring Batch>=4.1.0<=4.1.4
Broadcom Spring Batch>=4.2.0<=4.2.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    When configuring Jackson to enable default typing in Spring Batch, proactively block unknown "deserialization gadgets" (use Jackson’s gadget blacklisting so untrusted gadget classes are prevented from being deserialized).

    Spring Batch Jackson default typing (global default typing) = enable only with proactive blocking of unknown deserialization gadgets

Event History

Jun 11, 2020
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is CVE-2020-5411?

CVE-2020-5411 is a deserialization vulnerability in Jackson that could allow arbitrary code execution.

2

How does CVE-2020-5411 affect Spring Batch?

CVE-2020-5411 affects Spring Batch when it is configured with global default typing enabled.

3

What is the severity of CVE-2020-5411?

The severity of CVE-2020-5411 is high with a CVSS score of 8.1.

4

How can I fix CVE-2020-5411?

To fix CVE-2020-5411, update to a version of Spring Batch that contains the fix.

5

Where can I find more information about CVE-2020-5411?

You can find more information about CVE-2020-5411 at the following reference: [CVE-2020-5411](https://tanzu.vmware.com/security/cve-2020-5411)

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203