Arbitrary code execution via unbound serialized promises
Published Apr 29, 2024 · Updated Feb 13, 2025
Deserialization in R 1.4.0 through 4.3.3 allows remote attackers to execute arbitrary code through a crafted RDS file or R package. R_Unserialize accepts a serialized promise whose environment is the unbound-value marker, allowing its embedded expression to execute when the object is referenced. Execution requires a user or application to load and reference an attacker-controlled serialized object and runs with the R process's privileges.
Summary
What happened
Deserialization in R 1.4.0 through 4.3.3 allows remote attackers to execute arbitrary code through a crafted RDS file or R package. R_Unserialize accepts a serialized promise whose environment is the unbound-value marker, allowing its embedded expression to execute when the object is referenced. Execution requires a user or application to load and reference an attacker-controlled serialized object and runs with the R process's privileges.
The record
- CVE
- CVE-2024-27322
- Published
- Apr 29, 2024
- Updated
- Feb 13, 2025
- Vendor
- R Foundation for Statistical Computing
- Product
- R
- Classifications
- CWE-502, CAPEC-586, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=1.4.0 <4.4.0
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
- R-bitrary Code Execution 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