Relationships
#4842 cve extensions: data names can still collide or be refused on Windows (trailing dots, reserved device names, case)
Opened by stack72 · 11/17/2026
Found by the verify review for swamp-club #4834 (fix for #4831/#4832/#4833). After that change, instanceName in @swamp/cve/http2shell, php-rce-2026-10 and tailworm keeps only A-Za-z0-9._- (as sshole and emudhra do), but three Windows file-name rules are still not handled:
- Trailing dots: a target such as example.com. (FQDN with the root dot) is stored as example.com., which Windows strips to example.com, so it silently collides with a target example.com; logStatusClash does not notice.
- Reserved device names: a label CON, PRN, AUX, NUL, COM1-9 or LPT1-9 (any case, with or without an extension) is a name Windows refuses.
- Case: Windows file names are case-insensitive, so Web01 and web01 collide on disk, but logStatusClash compares names case-sensitively.
Suggested fix: strip or replace trailing dots and spaces, prefix reserved stems (e.g. _CON), and compare names case-insensitively in logStatusClash. Check sshole and emudhra too, since they share the allowlist approach.
Triaged
Click a lifecycle step above to view its details.
system commented 11/17/2026, 5:34:14 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.