shipshapecode / shipshapecode/angular-shepherd

vulnerability with deepmerge in shepherd.js

Open Beginner friendly
#2,987 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
238
Forks
50
Avg merge
1m
Merged PRs (30d)
9

Description

Hi,

┌───────────────┬──────────────────────────────────────────────────────────────┐
│ high │ DeepmergeTS has stack exhaustion when merging recursive │
│ │ object graphs │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ deepmerge-ts │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=8.0.0 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ angular-shepherd │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ angular-shepherd > shepherd.js > deepmerge-ts │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://www.npmjs.com/advisories/1145093
└───────────────┴──────────────────────────────────────────────────────────────┘

Just had this one in the building dependancies

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the angular-shepherd > shepherd.js > deepmerge-ts dependency path in the project manifests and lockfile. Confirm that the resolved deepmerge-ts version is at least 8.0.0, then run the existing build or test checks; done means the vulnerable dependency path is no longer present.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend, security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.