Code execution via unrestricted Jackson default typing
Published Jun 11, 2020 · Updated Sep 17, 2024
Deserialization of untrusted data in Spring Batch 4.2.0 through 4.2.2 allows attackers to execute code through a crafted ExecutionContext. Jackson2ExecutionContextStringSerializer enables global default typing, so Jackson resolves attacker-selected class names without restricting them to trusted types. Exploitation requires Jackson-based ExecutionContext storage and write access to the JobRepository data store; a loaded gadget executes code in the batch application process.
Summary
What happened
Deserialization of untrusted data in Spring Batch 4.2.0 through 4.2.2 allows attackers to execute code through a crafted ExecutionContext. Jackson2ExecutionContextStringSerializer enables global default typing, so Jackson resolves attacker-selected class names without restricting them to trusted types. Exploitation requires Jackson-based ExecutionContext storage and write access to the JobRepository data store; a loaded gadget executes code in the batch application process.
The record
- CVE
- CVE-2020-5411
- Published
- Jun 11, 2020
- Updated
- Sep 17, 2024
- Vendor
- Spring
- Product
- Spring Batch
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4 <4.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo