Arbitrary code execution via project package scripts
Published Jan 16, 2024 · Updated Jun 20, 2025
Resource injection in Meta Spark Studio before 176 allows attackers to execute arbitrary code when a user opens a crafted project. The project loader automatically runs lifecycle scripts declared in the included package.json without treating the project as untrusted content. Exploitation requires a user to obtain and open the project, after which the scripts run with the application's permissions and can read, alter, or delete accessible data.
Summary
What happened
Resource injection in Meta Spark Studio before 176 allows attackers to execute arbitrary code when a user opens a crafted project. The project loader automatically runs lifecycle scripts declared in the included package.json without treating the project as untrusted content. Exploitation requires a user to obtain and open the project, after which the scripts run with the application's permissions and can read, alter, or delete accessible data.
The record
- CVE
- CVE-2024-23347
- Published
- Jan 16, 2024
- Updated
- Jun 20, 2025
- Vendor
- Meta Platforms, Inc.
- Product
- Meta Spark Studio
- Classifications
- CWE-99, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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=0 <176
What conditions does exploitation require?
What is affected?
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