mapbox / mapbox/leaflet-omnivore

Moderate severity vulnerability

Open
#116 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
680
Forks
128
PR merge metrics
No merged PRs in 30d

Description

npm audit gives me a warning:

┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Moderate      │ Sandbox Breakout / Arbitrary Code Execution                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ static-eval                                                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=2.0.2                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ @mapbox/leaflet-omnivore [dev]                               │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ @mapbox/leaflet-omnivore > brfs > static-module >            │
│               │ static-eval                                                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/758                             │
└───────────────┴──────────────────────────────────────────────────────────────┘

Please update brfs to latest version :-)

Contributor guide

Open the contributing guide

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

No file or test is named. Start by running npm audit and tracing the reported @mapbox/leaflet-omnivore > brfs > static-module > static-eval path; the work is done when the dependency uses a version with static-eval >=2.0.2 and the warning is gone.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.