[Task] Review npm dependencies and update to releases past a 7-day quarantine

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
backend, security

Research direction

Start by reading server/package-lock.json and the dependency table; update listed packages to fixed versions after quarantine ends. Run npm audit --omit=dev and trivy fs --scanners vuln server/ to confirm clean scans. Run the pool test suite, then publish a patch release; done when lockfile updated and vulnerabilities resolved.

Written by the indexing model from the issue text.

Description

High priority NodeJS Security Task

Summary

Update the pool server's vulnerable npm dependencies to fixed releases that have passed a 7-day quarantine, and publish a patch release. Deployed pools run v3.1.1 (4be3b8a, the current dev). Its server/package-lock.json carries one critical and four high-severity packages, three of them on the public HTTP API.

Details

Trivy 0.76.1 on server/package-lock.json at 4be3b8a; the web/ and scripts/migrate-lowdb-mongodb/ lockfiles had no findings.

Package Locked Fixed Severity Advisories Pulled by Fixed release published
proxy-addr 2.0.7 2.0.8 critical CVE-2026-90711 express 2026-09-15
axios 1.18.1 1.20.0 7 high, 5 medium CVE-2026-101898, CVE-2026-101901, CVE-2026-101903, CVE-2026-101905, CVE-2026-101906, CVE-2026-101907, CVE-2026-101909, and 5 medium direct, adamant-api 2026-08-26
body-parser 2.3.0 2.4.0 high CVE-2026-111181 express 2026-10-22, quarantine ends 2026-10-29
follow-redirects 1.16.0 1.16.1 2 high CVE-2026-111755, CVE-2026-111756 axios 2026-10-01
socket.io-parser 4.2.6 4.2.7 high CVE-2026-69185 socket.io-client 2026-07-15
pbkdf2 3.1.6 3.1.7 medium CVE-2026-102414 adamant-api 2026-09-29
qs 6.15.3 6.16.0 2 medium CVE-2026-82417, CVE-2026-82562 body-parser, express 2026-08-29

express, with body-parser, proxy-addr and qs, serves the public voter dashboard and API, so its request-parsing issues are reachable from the internet. axios, follow-redirects and socket.io-client carry the pool's connections to ADAMANT nodes.

Checklist

  • Update the packages above in server/package-lock.json to their fixed releases, keeping the 7-day quarantine (body-parser 2.4.0 qualifies from 2026-10-29)
  • Re-check the web/ and scripts/migrate-lowdb-mongodb/ lockfiles
  • Run the pool test suite
  • Publish a patch release and list the dependency updates in its notes

Notes

  • The same axios, follow-redirects, body-parser, proxy-addr and socket.io-parser advisories affect the node: Adamant-im/adamant#281
  • Adamant-im/adamant#281 also describes tooling for the quarantine
  • Updating a deployed pool restarts it locked; payouts resume after the operator's unlock

Verification

  • npm audit --omit=dev in server/ reports no critical or high finding that has a fixed release
  • trivy fs --scanners vuln server/ no longer reports the advisories above
  • An updated pool restarts locked, and pays out after the operator's unlock
Dominant language
JavaScript
Stars
512
Forks
9
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from Adamant-im/pool

All issues in Adamant-im/pool

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.