-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Update marked version to 4 to avoid vulnerability #1852
Comments
Any reason to not update marked and close the vulnerability? |
There's no reason, just no one has gotten to it yet.
EDIT: I forgot, Marked was already updated beyond the above recommended version in #1993. But regardless, we are working to simplify and modernize Docsify and intend update We'll close this one in favor of that one. If someone feels like trying to update |
Marked was indeed already bumped to a version higher than the security vulnerabilities. Unfortunately, this was only done on the |
v5 is coming soon. In the meantime what you can do it simply clone Docsify, update marked version, run the build step, and host the built file with your static site. If someone has time to test it out for v4 prior to the breaking changes on develop (they are marked as breaking), and make a pull request for v4, we can consider that too. Personally when I circle back I will focus on the v5 release. |
@trusktr - Unfortunately, attempting a build off of
|
@gs-scooter If you would like to help out, ping us in Discord. |
Feature request
What problem does this feature solve?
The actual dependency on marked version 1.2.9, has a vulnerability of denial of service.
cf. CVE-2022-21681
Dependabot says it will be fixed if using marked >= 4.0.10
What does the proposed API look like?
How should this be implemented in your opinion?
Are you willing to work on this yourself?
I'm not an expert in js but i could try if needed
The text was updated successfully, but these errors were encountered: