-
Notifications
You must be signed in to change notification settings - Fork 2k
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
RCE possible in compat and strict mode #1736
Comments
This issue is getting flagged by security scanners (the commits have scary words in them it would seem). Can you clarify if these are indeed security fixes? Thanks in advance |
Yes, these are indeed security fixes, although only relevant in "compat" and "strict" mode. |
is there any plan to backport any relevant fixes to the 3.x branch, or is that line considered dead now? |
|
I've attempted a backport of these fixes to the 3.x release - #1751 . |
Note: v3.x is EOL and did not receive all relevant security fixes. Upgrade to at least v4.7.7. |
Two security issues have arised and are fixed in the referencing commits:
Due to insufficient escaping of the input template, it was possible to inject code into templates that are compiled in "compat" mode.
In "strict" mode, the exploits disclosed in the npm-security advisories 755,
1164, 1316,
1324 and 1325 and in the blog-article
of Mahmoud Gamal possible, because the the method that was used in strict-mode had not called the safe-guard methods.
The issues have been disclosed a couple of weeks ago at https://snyk.io/vuln/SNYK-JS-HANDLEBARS-1056767 and are fixed in version 4.7.7
The text was updated successfully, but these errors were encountered: