When.com Web Search

Search results

  1. Results From The WOW.Com Content Network
  2. Cross-site request forgery - Wikipedia

    en.wikipedia.org/wiki/Cross-site_request_forgery

    The web server will not be able to identify the forgery because the request was made by a user that was logged in, and submitted all the requisite cookies. Cross-site request forgery is an example of a confused deputy attack against a web browser because the web browser is tricked into submitting a forged request by a less privileged attacker.

  3. Cross-site leaks - Wikipedia

    en.wikipedia.org/wiki/Cross-site_leaks

    Cache-timing attacks rely on the ability to infer hits and misses in shared caches on the web platform. [54] One of the first instances of a cache-timing attack involved the making of a cross-origin request to a page and then probing for the existence of the resources loaded by the request in the shared HTTP and the DNS cache.

  4. JSONP - Wikipedia

    en.wikipedia.org/wiki/JSONP

    Naive deployments of JSONP are subject to cross-site request forgery (CSRF or XSRF) attacks. [12] Because the HTML <script> element does not respect the same-origin policy in web browser implementations, a malicious page can request and obtain JSON data belonging to another site. This will allow the JSON-encoded data to be evaluated in the ...

  5. HTTP response splitting - Wikipedia

    en.wikipedia.org/wiki/HTTP_response_splitting

    HTTP response splitting is a form of web application vulnerability, resulting from the failure of the application or its environment to properly sanitize input values.It can be used to perform cross-site scripting attacks, cross-user defacement, web cache poisoning, and similar exploits.

  6. Referer spoofing - Wikipedia

    en.wikipedia.org/wiki/Referer_spoofing

    Spoofing often allows access to a site's content where the site's web server is configured to block browsers that do not send referer headers. Website owners may do this to disallow hotlinking. It can also be used to defeat referer checking controls that are used to mitigate Cross-Site Request Forgery attacks.

  7. Session fixation - Wikipedia

    en.wikipedia.org/wiki/Session_fixation

    A logout function is useful as it allows users to indicate that a session should not allow further requests. Thus attacks can only be effective while a session is active. Note that the following code performs no Cross-site request forgery checks, potentially allowing an attacker to force users to log out of the web application.

  8. Cross-site scripting - Wikipedia

    en.wikipedia.org/wiki/Cross-site_scripting

    Cross-site scripting (XSS) [a] is a type of security vulnerability that can be found in some web applications. XSS attacks enable attackers to inject client-side scripts into web pages viewed by other users. A cross-site scripting vulnerability may be used by attackers to bypass access controls such as the same-origin policy.

  9. Talk:Cross-site request forgery - Wikipedia

    en.wikipedia.org/.../Talk:Cross-site_request_forgery

    Hidden form fields are the standard CSRF defense, and very effective assuming the browser is free of vulnerabilities and the site is free of cross-site scripting vulnerabilities. (These assumptions are reasonable because if they were not true, the attacker is unlikely to bother with CSRF as there are much easier attacks.)