[GHSA-qfjh-mvq6-c5p8] Jan path traversal vulnerability #4606
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
github-actions
bot
changed the base branch from
main
to
Van-QA/advisory-improvement-4606
|
Hi @Van-QA, do you have any reference links to support this claim? |
hi @CallmeMari, from the npm, you will no longer be able to find the @janhq/core package as Jan deprecated it. For Jan 0.5.2, can you advise on how to collect the evidence that Jan resolved the issue? Here is the PR of the fix from the dev team: janhq/jan#3152 Thank you, |
advisory-database
bot
merged commit b4bc8a2
into
Van-QA/advisory-improvement-4606
3 checks passed
|
Hi @Van-QA! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
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.
Updates
Comments
Jan resolved the issue in Jan v0.5.2, and deprecated the @janhq/core package. Could you kindly double-check if the problem still exists?