You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Security fix for possible Cross-site-scripting (XSS) attack #4353
@franciscojavierarceo The change that closed this issue (#4355) was reverted later in #4357. Shouldn't this issue be reopened? I can't find discussion about whether or not it worked or why it was reversed.
@jskrzypek yeah, you're right. I'll reopen the issue. The PR broke integration tests, that's why it was reverted. I'm not sure exactly why though, something about escaping special characters. We figured out that this PR was to blame for the failures a little too late, so most of the discussion was in Slack.
Thanks! Yeah, I was reading the changelog for 0.40.0 and saw both the fix: Avoid XSS attack... and then down below the Revert "fix: Avoid XSS attack..." so I got curious 😁
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
jskrzypek commentedon Aug 1, 2024
@franciscojavierarceo The change that closed this issue (#4355) was reverted later in #4357. Shouldn't this issue be reopened? I can't find discussion about whether or not it worked or why it was reversed.
tokoko commentedon Aug 1, 2024
@jskrzypek yeah, you're right. I'll reopen the issue. The PR broke integration tests, that's why it was reverted. I'm not sure exactly why though, something about escaping special characters. We figured out that this PR was to blame for the failures a little too late, so most of the discussion was in Slack.
jskrzypek commentedon Aug 2, 2024
Thanks! Yeah, I was reading the changelog for 0.40.0 and saw both the
fix: Avoid XSS attack...and then down below theRevert "fix: Avoid XSS attack..."so I got curious 😁stale commentedon Apr 26, 2025
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.