Relationships
#4844 cve/dirtyfrag: data names use the raw host or container label, with no sanitising or clash check
Opened by zack · 11/17/2026
Found while triaging swamp-club #4842. dirtyfrag_detect.ts in @swamp/cve/dirtyfrag writes status and log data under the raw target label (writeResource with status and host, createFileWriter with log and host-log, at about lines 854, 880, 921, 950, 1018 and 1224). Nothing sanitises it the way http2shell, php-rce-2026-10, tailworm, sshole and emudhra do. An IPv6 host, a host:port target or a docker image ref puts a colon in a data name, which Windows refuses. Two hosts that differ only in an unsafe character, or only in case, are never checked for a clash. Suggested fix: adopt the same instanceName/dataName allowlist and distinct-name check as the other cve extensions, including the Windows rules from #4842.
Open
No activity in this phase yet.
system commented 11/17/2026, 7:45:16 PM
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.