Unauthenticated command execution via unchecked Kryo deserialization
Published Dec 1, 2023 · Updated Aug 2, 2024
Deserialization in Jupiter 1.3.1 allows remote attackers to execute arbitrary commands through a crafted Kryo RPC request. The RPC provider's MessageTask.run() passes client-controlled object arguments to KryoSerializer, which invokes Kryo.readObject without class restrictions or security checks. Exploitation requires an object-accepting service method, compatible Commons Collections and BeanUtils gadgets, and remote class loading; success executes commands with the server process's privileges.
Summary
What happened
Deserialization in Jupiter 1.3.1 allows remote attackers to execute arbitrary commands through a crafted Kryo RPC request. The RPC provider's MessageTask.run() passes client-controlled object arguments to KryoSerializer, which invokes Kryo.readObject without class restrictions or security checks. Exploitation requires an object-accepting service method, compatible Commons Collections and BeanUtils gadgets, and remote class loading; success executes commands with the server process's privileges.
The record
- CVE
- CVE-2023-48887
- Published
- Dec 1, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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
- Jupiter Kryo deserialization proof of conceptproof of concept · 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