Remote code execution via forced pickle deserialization
Published Jul 8, 2022 · Updated Aug 3, 2024
Deserialization of untrusted data in rpc.py 0.4.2 through 0.6.0 allows remote attackers to execute code via an HTTP header. The get_serializer path honors a client-supplied serializer: pickle header and passes request data to Python unpickle despite JSON being the default. No authentication is required, so any network client reaching the RPC endpoint can achieve code execution with the server process privileges.
Summary
What happened
Deserialization of untrusted data in rpc.py 0.4.2 through 0.6.0 allows remote attackers to execute code via an HTTP header. The get_serializer path honors a client-supplied serializer: pickle header and passes request data to Python unpickle despite JSON being the default. No authentication is required, so any network client reaching the RPC endpoint can achieve code execution with the server process privileges.
The record
- CVE
- CVE-2022-35411
- Published
- Jul 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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
- rpcpy-exploitfunctional · 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