Tag Info

Hot answers tagged

28

After a bit of searching, it seems some banks are giving this advice following an attack on a bank that allowed users or malicious websites to reuse persistent cookies after a user had logged out, allegedly because other browser tabs were left open on the site in question and so the browser had not cleared the cookies yet. The reason such a vulnerability ...


8

You should close your web browser (to avoid private information disclosure) if... Someone might access the computer after you do The HTTP response (of the sensitive info) does not set the Cache-Control header properly For example, go to yourbank.com, and look at your account. Click logout. Click the back button. Do you see your account info? On some ...


5

It's in the page source, nested in an HTML table cell as: <td width="194" height="34" class="poll_row_border" style="padding-left:4px;"><div align="right" class="tool_description"> "><ScRipT>alert(31337)</ScrIpT> </div></td> Interestingly, there are two sets of similar code that ...


5

The full URL (hostname and path) is only inside the HTTP protocol and is thus encrypted by the TLS layer. Also, any HTTP headers and payload of request and response are end-to-end encrypted. But, the hostname part of the URL is usually in the CONNECT request when using a non-transparent HTTP proxy, unless the client itself makes the DNS lookup. With a SOCKS ...


4

Avoiding attacks on your site You need to validate that the string you received is valid. Remember this principle: you must white-list acceptable strings rather than black-list unacceptable ones. Ensure that the string is a syntactically-correct and escaped URL. Escaping the whole URL avoids it containing " or > which could break your site's syntax. ...


4

Yes, both GET and POST are vulnerable to CSRF. However, RFC 2616 states the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered "safe". Therefore, if a website has kept to the standard and only implements "unsafe" actions as POSTs, then here only POST requests are ...


3

Yes it can be an issue but there are ways for applications to protect against it. Two sides to every internet application. In order to understand internet application security you have to understand the difference between the client and the server. Data which is generated by the client (the browser), must be sanitized and validated before being by the ...


3

This advice is often given for Single Sign On (SSO) solutions. This is for a collection of systems, where a user only logs in once. The authentication of the user is handled by a central system called the Identity Provider. After login, two sessions are established with the requested system and with the Identity Provider itself. When visiting a new system ...


3

There are two main types of issues that can occur with client-side execution: A malicious client can modify their client state and attempt to make the server accept that modified state as valid An unsuspecting user can be tricked into running code in their console by a malicious third-party, something caused Self XSS Malicious clients running ...


2

You should use the private directive. Note that content will remain available within the user's browser, even if the Expires header is set as this header does not necessarily force the browser to purge it after the date and time set so it does not meet your session time-out requirement. However, if this risk is acceptable then it may be suitable. You could ...


2

With enough traffic from your internal users, an attacker could map the internal networks of an organization. There might be very low value in this data, however, if DHCP expires IPs quickly, or if the internal network is predictable (or uninteresting) on its own. It would also require a lot of traffic from the network's users to be helpful.


2

GET and POST can both be vulnerable to CSRF unless the server puts a strong Anti-CSRF mechanism in place, the server cant rely on the browser to prevent cross-domain requests. As for PUT requests, there is a slight difference, theoretically it is vulnerable too, however, it requires the circumstances to be more conducive. Here is why: While GET and POST ...


1

My website was also infected with adsmatte problem. when user opened it in mobile device it just opened a bunch of spam ads. and when on PC, it opened popups. I researched a lot and finally tried a suggestion i read on one of the forums. Check every SCRIPT by disabling it. I did that and found the real culprit for my website was 'Sharethis.com' widget. I ...


1

This technique is often used when a website uses basic or windows authentication since there isn't a way to "log out". Instead of using cookies, the authentication mechanism is added as an Authorization header to every request sent to the website. For basic authentication it would be the username/password in a base64 encoded string and for windows ...


1

The method; i.e. put, post, delete, request, get etc., of sending data is irrelevant. A CSRF (Cross Site Request Forgery) attack allows for un-trusted content to be injected and processed by the web server.


1

I have been suffering from this virus for last seven days, but in my android tablet. I have formatted my tablet three times in three days, but problem reoccurs just after installing the browser. It is correct that it alters your DNS server address. I have read a post somewhere in the xda forums that gave me hint about this: go to wifi settings and find the ...


1

If your router is affected and you're facing different issues on your devices (android has no ads, computer does) may check/change your DNS settings on both devices and on the rooter. I think you android phone uses a different DNS server as your PC. Your PC propably uses your Router as DNS Server (e.g. 196.168.1.1) and your android uses a 3rd party DNS like ...


1

This does not appear to be an OS/browser related issue. I would recommend you to read this http://www.quora.com/How-do-I-stop-AdsMatte-spam-popups-and-ads What it says: I believe all your default gateways is "192.168.1.1" Open this from your PC. If you can't open it, the the solution below must work: I believe you should know about it first(skip ...


1

I ran into this issue not too long ago. If you have done a clean OS install then it is likely that your Chrome settings have been tampered with, infected, auto-backed up, and restored once you log into Chrome again after the clean install. You can try and reset your Chrome settings. It actually took me hitting this more than once and manually inspecting my ...


1

Todays used fingerprints mostly rely on generating as much entropy as possible by exploiting as much details of the browser as they can. Even subtle, but short term stable details, like the exact (hardware and driver version dependent) rendering on a canvas is exploited. The information gathered is most likely compressed by generating a long enough hash ...


1

Configure your browser to point to Burp's proxy details (e.g. 127.0.0.1:8080) and then configure Burp to use an upstream HTTP proxy for all target hosts (* as the destination): However, if the upstream proxy is SOCKS, not HTTP, you need to configure it underneath (under the SOCKS Proxy heading) instead. This causes everything to be fed through the proxy. ...



Only top voted, non community-wiki answers of a minimum length are eligible