CVE-2024-23347
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPrior to v176, when opening a new project Meta Spark Studio would execute scripts defined inside of a package.json file included as part of that project. Those scripts would have the ability to execute arbitrary code on the system as the application.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMeta Spark Studio versions prior to v176 execute scripts defined in package.json files when opening a project, allowing attackers to achieve arbitrary code execution with the application's privileges by embedding malicious scripts in a project's package.json.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 176CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Meta Spark Studio installationLocate the Meta Spark Studio application on the system. Common locations include Program Files (Windows) or Applications folder (macOS). Check for the presence of spark.exe (Windows) or Spark Studio.app (macOS).Affected if Meta Spark Studio is installed on the system
-
Determine installed versionOpen Meta Spark Studio and navigate to the application menu, then select 'About Spark Studio' or 'About Meta Spark Studio' to view the version number. Alternatively, check the application's metadata file in the installation directory.Affected if The displayed version number is less than 176
-
Compare version against affected rangeIf the version is displayed numerically (e.g., 175, 174, 173), compare it to the vulnerable threshold. Versions prior to v176 are affected.Affected if Installed version is less than 176 (e.g., 175, 174, 170, etc.)
-
Confirm vulnerability conditionIf both conditions are met: (1) Meta Spark Studio is present and (2) version is below 176, the environment is affected by CVE-2024-23347.Affected if Meta Spark Studio is installed with version < 176
The environment is affected if Meta Spark Studio is installed and the version number is lower than 176, as versions prior to v176 automatically execute scripts from package.json files, enabling arbitrary code execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped176
Update to Meta Spark Studio v176 or later, which disables automatic execution of scripts from package.json files.
Meta Spark Studio v176
- Check the current version of Meta Spark Studio by opening the application and navigating to Help > About Meta Spark Studio
- Download Meta Spark Studio version 176 or later from the official Meta Spark website or within the application if an update option is available
- Install the updated version to resolve the arbitrary code execution vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23347 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data