dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-38990

MEDIUM · 6.3 CVSS v3.1 Published 2024-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Tada5hi sp-common v0.5.4 was discovered to contain a prototype pollution via the function mergeDeep. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

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 confidence

The Tada5hi sp-common library v0.5.4 contains a prototype pollution vulnerability in the mergeDeep function. Attackers can inject arbitrary properties into JavaScript objects by exploiting this function, potentially leading to arbitrary code execution or denial of service by manipulating the object prototype chain.

MitigationUpdate to a patched version of sp-common when available. As an interim measure, validate and sanitize all inputs before passing them to mergeDeep, specifically blocking __proto__, constructor, and prototype property names.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the sp-common package in your project dependencies
    Search for 'sp-common' in your package.json file or check node_modules/@tada5hi/sp-common if using scoped packages
    Affected if The package is present in your project
  2. Identify the installed version of sp-common
    Run 'npm list @tada5hi/sp-common' or check the version field in package.json under sp-common dependencies
    Affected if The version listed is exactly 0.5.4
  3. Find usage of the mergeDeep function in your codebase
    Search your source code for imports or requires of mergeDeep from sp-common, for example: 'import { mergeDeep } from @tada5hi/sp-common' or similar patterns
    Affected if The mergeDeep function is imported and used in your code
  4. Inspect inputs passed to mergeDeep calls
    Review all function calls passing data to mergeDeep and examine whether untrusted user input reaches these calls, especially checking for property names containing __proto__, constructor, or prototype
    Affected if User-controlled or unsanitized data is passed to mergeDeep without filtering those special property names

You are affected if sp-common version 0.5.4 is installed AND the mergeDeep function is being used with untrusted or unsanitized input that could contain __proto__, constructor, or prototype property names.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of sp-common when available. As an interim measure, validate and sanitize all inputs before passing them to mergeDeep, specifically blocking __proto__, constructor, and prototype property names.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38990 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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