-
Notifications
You must be signed in to change notification settings - Fork 3.3k
fix(messaging): stop merge tags inserting double quotes #91352
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
Open
posthog
wants to merge
2
commits into
master
Choose a base branch
from
posthog-self-driving/fixmessaging-stop-merge-tags-inserting-414661
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+32
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
buildPersonPropertyMergeValue()(frontend/src/scenes/hog-functions/email-templater/emailTemplaterLogic.tsx:161-167) only escapes backslash and single-quote characters before embedding the property name inside{{person.properties['...']}}. It does not escape{or}.property.namecomes fromPropertyDefinitions loaded fromloadPersonPropertyDefinitions(line ~486), which reflects arbitrary person-property keys captured from real ingested events — i.e. any unauthenticated visitor hitting the project's public capture endpoint can set a person property whose name contains}}or{{. When an org member later opens the merge-tag menu and inserts that property, the generated string, e.g. for a name likefoo}} <img src=x onerror=alert(1)> {{bar, becomes{{person.properties['foo}} <img src=x onerror=alert(1)> {{bar']}}, which is saved verbatim into the stored email template HTML.At render time,
LiquidRenderer.renderWithHogFunctionGlobals(nodejs/src/cdp/utils/liquid.ts) uses the non-greedy regex/\{\{(.*?)\}\}/to find and entity-decode Liquid tags, then callsliquid.parseAndRenderSync. Because Liquid's tag scanner also looks for the first literal}}, the injected}}prematurely closes the tag; the attacker's HTML/script payload then sits as literal template markup outside any{{ }}expression, so LiquidJS'soutputEscape: 'escape'(which only escapes resolved values, not literal template bytes) never touches it — it is emitted unescaped into every email sent from that template, reaching the org's real customers. Since this PR explicitly rewrites the merge-tag emission specifically to close an HTML/Liquid-breakout bug, the new escaping should also neutralize{and}(e.g. reject/strip them, or refuse bracket-notation for names containing them and fall back to a safe placeholder) rather than only guarding against straight double quotes.Severity: medium | Confidence: 45% | React with 👍 if useful or 👎 if not