Export Record - No Output Seen for txt/doc

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download | Install latest version, .717
2. Load URL http://cloudscan.org

What is the expected output? What do you see instead?

I run DOMSnitch against the URL http://cloudscan.org and see the output that 
says an untrusted source....  when I export to TXT | Doc.. the output it empty.

What version of the product are you using? On what operating system?

UA = 13.0.782.218 m, OS = Windows 2008 R2 Server 64 Bit, untested on other OS 
platforms.

Please provide any additional information below.

Global.URL for baseline transaction = http://cloudscan.org and results are 
posted in Issue #21, DOMSnitch still not fingerprinting the issues with no 
output for an exported record to TXT | Doc.

Original issue reported on code.google.com by [email protected] on 1 Sep 2011 at 11:45

[GoogleCodeExporter]

Original comment by [email protected] on 1 Sep 2011 at 4:18

• Changed state: Accepted

[GoogleCodeExporter]

Thanks for your quick response! The export might be due to schema changes in 
the DB. Can you clear the activity log and re-run your test? 

I've re-opened Issue 21 to track it separately.

Original comment by [email protected] on 1 Sep 2011 at 4:29

[GoogleCodeExporter]

Hi!

Repro (latest download)..

1. Open UA
2. Clear Logs
3. Close UA
4. Open UA
5. Load Global.URL http://cloudscan.me
6. Right click, confirm DOMsnitch is enabled
7. Right Click, View log
8. See ID #1 + #2, click on the yellow highlight
9. Reading Security Notes.. Loading of CSS from an untrusted origin.
10. Click on Export Record to TXT .. result.. blank
11. Click on Export Record to Doc .. result.. blank
12. Export All, result .. blank

Tried opening, closing, tried incogneto, same results. also cleared local 
history, cookies etc... just trying to click and clear my way to a clean 
export.. no luck ..

Happy to post vid to youtube if you want.. whatever works..

Great tool you all are working on!

-D

Original comment by [email protected] on 1 Sep 2011 at 4:47

[GoogleCodeExporter]

Hi!

I meant to add, eval() isn't marking either.. gmail to // h02332 _if_ you want 
a private PoC.. but I've got a few examples with eval and other low hanging 
fruit.. 

-D

Original comment by [email protected] on 1 Sep 2011 at 4:51

[GoogleCodeExporter]

Here is an example expression:

#%0Afunction Xss(){alert('XSS')%3B}

I've got a Site that permits that function, the assumption is, using DOMinator 
as the example, that when that gets eval'd, DOMSnitch should see the issue and 
report it to a logfile, where then I can export it and work with the devs on 
repro.

Let me know if/how else I can help;

-D
... Xss()

Original comment by [email protected] on 1 Sep 2011 at 4:57

[GoogleCodeExporter]

Pictures!

screen grabs attached, left to right presentation.. on left is Chrome, on right 
is DOMinator.. point of screen grab is to show output from tools..

GOAL: I'm hoping to export the records to TXT or Doc. See screen grab #2 for 
the results of the Record Export to TXT.

-D

Original comment by [email protected] on 1 Sep 2011 at 5:05

Attachments:

• dominator-vs-domsnitch-output-cloudscanorg-1.JPG
• domsnitch-export-record-results-1.JPG

[GoogleCodeExporter]

Export Records - Resolved (Partial)

Repro Steps
=======================
Removed DOMSnitch
Closed UA
Open Ua
Reinstall DOMSnitch
Clear Logs
Close UA
Open UA
Open Global URL http://cloudscan.org
Success on Export to TXT
Clicked on Export to Doc ... (Redirecting) hang..

-D

Original comment by [email protected] on 1 Sep 2011 at 5:27

[GoogleCodeExporter]

Thanks for the the details. For the exporting issue, can you click "clear all" 
in the top right corner of the activity log? Once you've done that, please try 
again running your test. What I'm suspecting to have happened is the 
StorageWorker.js throwing an error because of slight discrepancy in the SQLite 
schema between 0.707 and 0.717.

As for the heuristic, I see what you mean w.r.t. the location issue. The 
current issue you're seeing is that you're loading code from a 3rd party 
server, which is outside of your control (which is something sites that hold 
user data may care about). It is not directly related to the fact that the 
script is assigning user input into document.location. I haven't implemented 
yet a heuristic for catching assignments into document.location. It is 
something on the list of things to get added, so thank you for bringing it up! 
:)

Original comment by [email protected] on 1 Sep 2011 at 8:10

[GoogleCodeExporter]

Re: the reporting format, I'm currently not using the V8 debugger. Once I start 
using it, the tool would be able to provide the level of detail that 
researchers would be interested in. I've covered this topic a bit further here: 
http://radi.r-n-d.org/2011/07/on-dom-snitch-internals-and-some-of.html (namely, 
topic #2).

Original comment by [email protected] on 1 Sep 2011 at 8:12

[GoogleCodeExporter]

Hi-

w/r/t exporting to txt.. as noted, working fine as Plain text export for record 
n
w/r/t exporting to Docs.. no love..

Repro
------------
(todays chrome and domsnitch.. os= w2008r2.server|64bit)

Opened UA
Cleared Log
Closed UA
Opened UA
Removed DOMSnitch
Close UA
Open UA, confirm removal
Download, Install DOMSnitch in Chrome
Close UA
Open UA
Clear Log
Close UA
Open UA
Load URL http://cloudscan.org
Right Click, Confirm DOMSnitch on (all on) and then view log
Click into issue, export to Txt, confirmed, works! :-)
Click into issue,export to Doc, wait (wait.. wait).. waited.. close UA
Update Ticket

All good.. its least its a known feature on windows 2008 r2 server... ;-)

Let me know how else I can help..

-D

Original comment by [email protected] on 1 Sep 2011 at 9:27