First published: Thu 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.
Credit: security@pivotal.io
Affected Software | Affected Version | How to fix |
---|---|---|
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-5411 is a deserialization vulnerability in Jackson that could allow arbitrary code execution.
CVE-2020-5411 affects Spring Batch when it is configured with global default typing enabled.
The severity of CVE-2020-5411 is high with a CVSS score of 8.1.
To fix CVE-2020-5411, update to a version of Spring Batch that contains the fix.
You can find more information about CVE-2020-5411 at the following reference: [CVE-2020-5411](https://tanzu.vmware.com/security/cve-2020-5411)