Skip to main content
← Back to list
01Issue
BugShippedExtensionsPublic
Assigneesstack72

Relationships

#3762 @swamp/cve/dirtyfrag report suggests commands for dirtyfrag-scanner whatever the model is named

Opened by stack72 · 10/22/2026· Shipped 10/22/2026

The scan and mitigate report in @swamp/cve/dirtyfrag (extensions/reports/dirtyfrag_scan_report.ts, 2026.10.22.1) hardcodes the model name dirtyfrag-scanner in every follow-up command it prints (To apply, Verify with, Next Step). Since the README now has users create one model per target with --global-arg (dirtyfrag-web, dirtyfrag-fleet, dirtyfrag-container), copying the suggested command runs against the wrong model, or one that does not exist, and so with the wrong SSH user and key. The Next Step block also builds --input hosts from each result's hostname (e.g. ip-172-31-35-99, the remote host's own name) rather than the address it was scanned at, so on a fleet scanned by IP the suggested hosts list may not resolve. Expected: use the running model's name and the scanned address. Found while triaging swamp-club #3761.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 11 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

10/22/2026, 2:16:29 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack7210/22/2026, 1:36:11 AM
Editable. Press Enter to edit.

system commented 10/22/2026, 1:30:59 AM

Classified automatically when this issue was filed.

  • Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

Sign in to post a ripple.