CVE-2024-24294
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 · uneditedA Prototype Pollution issue in Blackprint @blackprint/engine v.0.9.0 allows an attacker to execute arbitrary code via the _utils.setDeepProperty function of engine.min.js.
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 · moderate confidenceBlackprint engine v0.9.0 contains a Prototype Pollution vulnerability in the _utils.setDeepProperty function. This allows an attacker to inject or modify properties on JavaScript object prototypes, potentially leading to arbitrary code execution via engine.min.js.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify if Blackprint engine is installedSearch your project for @blackprint/engine in package.json dependencies, or check node_modules/@blackprint/engine for the presence of the engine filesAffected if @blackprint/engine is found in dependencies or node_modules
-
Check the installed version of @blackprint/engineRun 'npm list @blackprint/engine' or inspect the version field in package.json for @blackprint/engineAffected if The version is exactly v0.9.0 or falls within the v0.9.0 range
-
Locate the setDeepProperty function in the codebaseSearch for '_utils.setDeepProperty' or 'setDeepProperty' in your Blackprint engine files or imported modulesAffected if The setDeepProperty function from _utils exists and is accessible in your environment
-
Determine if user input reaches setDeepPropertyInspect code that calls setDeepProperty and trace whether any user-controlled data (request parameters, API input, imported JSON) flows into this function as the property path argumentAffected if User input or untrusted data is passed to setDeepProperty without sanitization
-
Check if engine.min.js is accessible in your deploymentVerify that engine.min.js from the Blackprint engine package is present in served static files or accessible endpointsAffected if engine.min.js is deployed and accessible to end users or untrusted code
Your environment is affected if @blackprint/engine version 0.9.0 is installed AND user input can reach the setDeepProperty function without validation, allowing prototype pollution injection.
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.
From vendor dataUpgrade to a patched version of @blackprint/engine that properly validates or sanitizes input in the setDeepProperty function, or implement input validation to prevent prototype pollution attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24294 — 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-24294 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