-
-
Notifications
You must be signed in to change notification settings - Fork 730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: don't allow . or .. in feature url #8479
Merged
Tymek
merged 2 commits into
main
from
1-2986-some-invalid-flag-names-arent-caught-by-validation-eg
Oct 21, 2024
Merged
fix: don't allow . or .. in feature url #8479
Tymek
merged 2 commits into
main
from
1-2986-some-invalid-flag-names-arent-caught-by-validation-eg
Oct 21, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
Tymek
commented
Oct 18, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this change applies to features, tags, projects, context fields and addons
Tymek
changed the title
1 2986 some invalid flag names arent caught by validation eg
fix: don't allow . or .. in feature url
Oct 18, 2024
...aginatedProjectFeatureToggles/ProjectFeatureTogglesHeader/hooks/useFeatureCreatedFeedback.ts
Outdated
Show resolved
Hide resolved
Comment on lines
+17
to
+19
encodeURIComponent(value) !== value || | ||
value === '..' || | ||
value === '.' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tymek
force-pushed
the
1-2986-some-invalid-flag-names-arent-caught-by-validation-eg
branch
from
October 21, 2024 13:59
639818b
to
24789d2
Compare
thomasheartman
approved these changes
Oct 21, 2024
Tymek
deleted the
1-2986-some-invalid-flag-names-arent-caught-by-validation-eg
branch
October 21, 2024 14:35
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We do some validation on flag names, but there's some cases that slip through. These are some cases that we should handle better.
With
..
as a name, you can't go into the flag in Unleash and you can't activate any environments because the it is interpreted as "go up a level".