Skip to content

fix: ensure separator boundary in allowFsRead wildcard check#3967

Open
fg0x0 wants to merge 1 commit intoparallax:masterfrom
fg0x0:fix/allowfsread-separator-boundary
Open

fix: ensure separator boundary in allowFsRead wildcard check#3967
fg0x0 wants to merge 1 commit intoparallax:masterfrom
fg0x0:fix/allowfsread-separator-boundary

Conversation

@fg0x0
Copy link
Copy Markdown

@fg0x0 fg0x0 commented Mar 19, 2026

This patch addresses the path prefix confusion in the allowFsRead wildcard handling reported via security disclosure.

The original condition checked whether fixedPart ended with path.sep before appending a separator to resolved. On Windows, path.sep is a backslash, but wildcard patterns are typically written with forward slashes (e.g. ./fonts/*), so the condition was never true and no separator was appended.

The fix removes the fixedPart check entirely. Since path.resolve() already normalizes the separator to the OS-native character, checking resolved alone is both sufficient and correct on all platforms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant