fix(security): Fix security issue in handlebars via minor version upgrade from 4.7.8 to 4.7.9#1708
Draft
aikido-autofix[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
This file contains hidden or 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
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.
Upgrade Handlebars to fix critical RCE via AST injection, medium proto-access bypass, and low TOCTOU property lookup vulnerability.
✅ 3 CVEs resolved by this upgrade, including 1 critical 🚨 CVE
This PR will resolve the following CVEs:
Handlebars.compile()allows attackers to inject arbitrary JavaScript through crafted AST objects, enabling Remote Code Execution when theNumberLiteralvalue field is emitted without sanitization.__lookupSetter__while blocking its symmetric counterparts, allowing prototype pollution when the non-defaultallowProtoMethodsByDefault: trueoption is set. This creates an inconsistent security boundary enabling potential code execution or object manipulation through template injection.lookup()function allows prototype pollution and property access bypass when the compat option is enabled, potentially leading to information disclosure or code execution. The security check vialookupProperty()is discarded, and an unguarded property access is performed instead.