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.
fix(security): add path traversal validation to widget save path (GHSA-r553-q33m-v7pf) #41834
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
base: release
Are you sure you want to change the base?
fix(security): add path traversal validation to widget save path (GHSA-r553-q33m-v7pf) #41834
Changes from all commits
602dc22eff0ba7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
Pre-clean the traversal artifact and tighten the expected exception type.
Two small hygiene gaps in this regression test:
Files.exists(Path.of("/tmp/ghsa-r553-traversal-test.json"))is not guarded against pre-existing state. If a prior run (with a regressed fix, or any unrelated process) left that file on disk, this assertion fails spuriously even when the current code is correct. Delete it before the action so the test is self-contained.assertThrows(RuntimeException.class, ...)is broader than necessary — the fix throwsAppsmithPluginException. Asserting the specific type prevents an unrelatedNullPointerException/RuntimeExceptionfrom masquerading as a passing security test.🛡️ Proposed tightening
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.