Remote code execution via unsafe HTTP deserialization
Published Jan 2, 2020 · Updated Aug 6, 2024
Unsafe deserialization in Pivotal Spring Framework before 6.0.0 allows remote attackers to execute code through an HTTP Invoker endpoint. HttpInvokerServiceExporter.readRemoteInvocation wraps the request body in an ObjectInputStream and calls readObject before confirming that the result is a RemoteInvocation. Exploitation requires an exposed endpoint and a usable gadget chain on the application classpath; authentication depends on the host application's configuration.
Summary
What happened
Unsafe deserialization in Pivotal Spring Framework before 6.0.0 allows remote attackers to execute code through an HTTP Invoker endpoint. HttpInvokerServiceExporter.readRemoteInvocation wraps the request body in an ObjectInputStream and calls readObject before confirming that the result is a RemoteInvocation. Exploitation requires an exposed endpoint and a usable gadget chain on the application classpath; authentication depends on the host application's configuration.
The record
- CVE
- CVE-2016-1000027
- Published
- Jan 2, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- HTTP Invoker ysoserial gadget-chain demonstrationfunctional · demonstrated
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