DOM XSS

463 posts

DOM XSS

DOM XSS

@DOMXss

We retweet your #DOMXSS news and findings

Katılım Mart 2011
0 Takip Edilen1.6K Takipçiler
DOM XSS retweetledi
koto
koto@kkotowicz·
DOM #XSS, it's time to say goodbye. See the newest status update on Trusted Types, delivered at #w3ctpac. The simplest polyfill is a tiny TrustedTypes={createPolicy:(n,rules)=>rules} (yes, that can help end DOM XSS), but there's so much more good news! tinyurl.com/tttpac
English
2
47
98
0
DOM XSS retweetledi
ISWAT
ISWAT@ISWATLAB·
[RecentQuestions] Is this code vulnerable to DOM based XSS jquery animate? dlvr.it/Qv7wRy [sec.stackexchange]
English
0
2
3
0
DOM XSS retweetledi
JSFoo
JSFoo@jsfoo·
"At @GoogleVRP, DOM based cross-site scripting is already the most common variant of XSS" @lavakumark
English
0
2
3
0
DOM XSS retweetledi
RIVER
RIVER@wugeej·
[Tool] XSStrike v3.0 - Most Advanced XSS Detection Suite Reflected and DOM XSS Scanning Multithreaded crawling Context analysis Configurable Core Highly Researched Workflow WAF detection & evasion Handmade HTML & JavaScript parser Powerful fuzzing engine github.com/s0md3v/XSStrike
English
0
2
4
0
DOM XSS retweetledi
Anant Shrivastava
Anant Shrivastava@anantshri·
Intelligent work by @lavakumark in DOMGO.AT selecting debug flag enables pre assigned debug locations to facilitate understanding of domxss working.
Anant Shrivastava tweet media
English
0
4
4
0
DOM XSS retweetledi
Mohamed Haron
Mohamed Haron@m7mdharon·
Seems that Hackerone staff give duplicate for the good reports and when you ask an invite to the main report .. the response is great too ( not duplicate) hackerone.com/reports/405191
English
0
1
3
0
DOM XSS retweetledi
n00py
n00py@n00py1·
Poll for web app testers: when Burp finds DOM XSS via static code analysis, how often do you find that you can exploit it?
English
1
2
0
0
DOM XSS retweetledi
harisec
harisec@har1sec·
@0x6D6172696F DOM XSS inside an iframe via postMessage (the iframe is included in the main page, but hidden). What is the impact in this case OR is there an impact in this case?
English
0
1
2
0
DOM XSS retweetledi
koto
koto@kkotowicz·
@fenceposterror And in general I don't think we are struggling with XSS because sanitization is hard. It's hard because the DOM APIs are insecure by default and in the end we end up with DOM XSS everywhere.
English
0
1
0
0