[DepShield] (CVSS 7.4) Vulnerability due to usage of ini:1.3.5
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- build-system, security
Research direction
Start by tracing the listed direct dependencies—gulp, gulp-imagemin, and nodemon—to locate the dependency manifest and lockfile entries that bring in ini:1.3.5. Done means the dependency tree no longer resolves to the vulnerable ini version and the project's dependency checks still pass.
Written by the indexing model from the issue text.
Description
Vulnerabilities
DepShield reports that this application's usage of ini:1.3.5 results in the following vulnerability(s):
Occurrences
ini:1.3.5 is a transitive dependency introduced by the following direct dependency(s):
• gulp:4.0.2
└─ glob-watcher:5.0.3
└─ chokidar:2.1.8
└─ fsevents:1.2.12
└─ node-pre-gyp:0.14.0
└─ rc:1.2.8
└─ ini:1.3.5
└─ gulp-cli:2.2.0
└─ liftoff:3.1.0
└─ findup-sync:3.0.0
└─ resolve-dir:1.0.1
└─ global-modules:1.0.0
└─ global-prefix:1.0.2
└─ ini:1.3.5
• gulp-imagemin:7.1.0
└─ imagemin-gifsicle:7.0.0
└─ gifsicle:5.0.0
└─ bin-build:3.0.0
└─ download:6.2.5
└─ caw:2.0.1
└─ get-proxy:2.1.0
└─ npm-conf:1.1.3
└─ config-chain:1.1.12
└─ ini:1.3.5
• nodemon:2.0.2
└─ update-notifier:2.5.0
└─ is-installed-globally:0.1.0
└─ global-dirs:0.1.1
└─ ini:1.3.5
└─ latest-version:3.1.0
└─ package-json:4.0.1
└─ registry-auth-token:3.4.0
└─ rc:1.2.8
└─ ini:1.3.5
This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.
- Dominant language
- EJS
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mog-rn/codespace
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
All issues in mog-rn/codespace
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
HarperFast/harper#2860 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
anthropics/skills#1893 · 1 comment ·
Maintainers usually reply within 1 day
-
pnpm install exits 1: MemoryCore/pnpm-workspace.yaml ships "set this to true or false" placeholdersOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TencentCloud/TencentDB-Agent-Memory#1544 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
YosysHQ/oss-cad-suite-build#216 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openwatersio/slackwater.xyz#124 ·
Maintainers usually reply within 1 day