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 }}
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.
When sending a request to an address it seems the address is evaluated by webkit before the request goes through our request & whitelist logic.
A request to http://rim.com', http://rim.com%, http://rim.com& and a few other combinations including possible XSS attacks such as http://rim.com');console.log('btw I can remotely execute code in your app');// will direct to a different page displaying an _Error: This webpage is unavailable. Check the URL and try again.
When a request to a non-address like ');alert('asd');// it also directs to a different page with Error This file could not be opened. Check that you have the correct permissions and try again.
A request to http://rim.com# will result in a a request to http://rim.com/#
I haven't tested all possibilities but I just wanted to point out this separate issue that I have come across while investigating the current XSS issue.
I've tried a couple possible XSS attacks that I come up with but I have not been able to do so successfully mainly do to the above issue I am having where requests never make it to our framework logic.
See gtanner's comment in blackberry-webworks#18
The text was updated successfully, but these errors were encountered: