stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Block releases with vulnerable runtime dependencies #988

New Issue
Closed
opened 2026-08-16 21:00:13 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-16 21:00:13 +00:00
Member
Copy Link

Evidence

requirements.txt pins python-multipart==0.0.22, while current advisories affect multipart/form parsing used by the dashboard attachment endpoints. The CI workflow installs runtime dependencies and runs tests but has no dependency vulnerability gate, so known-vulnerable packages can reach a release candidate. No open or historical issue title covers multipart dependency hardening or a dependency audit gate.

User impact

Malformed form or attachment requests must not expose operators to known parser denial-of-service flaws, and future known-vulnerable runtime pins must block release promotion.

Acceptance criteria

  • Upgrade python-multipart to a release not affected by the currently published advisories.
  • Add a reproducible, pinned dependency audit command for the shipped runtime dependency set.
  • Make CI run that audit before release bundle construction; release publication remains transitively dependent on it.
  • Add behavioral workflow tests first and demonstrate RED before implementation.
  • Focused tests and the complete test suite pass.
## Evidence `requirements.txt` pins `python-multipart==0.0.22`, while current advisories affect multipart/form parsing used by the dashboard attachment endpoints. The CI workflow installs runtime dependencies and runs tests but has no dependency vulnerability gate, so known-vulnerable packages can reach a release candidate. No open or historical issue title covers multipart dependency hardening or a dependency audit gate. ## User impact Malformed form or attachment requests must not expose operators to known parser denial-of-service flaws, and future known-vulnerable runtime pins must block release promotion. ## Acceptance criteria - Upgrade `python-multipart` to a release not affected by the currently published advisories. - Add a reproducible, pinned dependency audit command for the shipped runtime dependency set. - Make CI run that audit before release bundle construction; release publication remains transitively dependent on it. - Add behavioral workflow tests first and demonstrate RED before implementation. - Focused tests and the complete test suite pass.
timmy was assigned by rockachopa 2026-08-16 21:00:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#988
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?