Questions about this topic? Sign up to ask in the talk tab.
Difference between revisions of "XSCF"
From NetSec
GertieUbpgdd (Talk | contribs) |
|||
| (10 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{expand}} | ||
| + | {{merge|XSS}} | ||
| + | =Introduction= | ||
<b>C</b>ross-<b>S</b>ite <b>C</b>ontent <b>F</b>orgery is a [[vulnerability]] class that entails malforming the server-side mimetype for a particular resource to make it appear as something else. | <b>C</b>ross-<b>S</b>ite <b>C</b>ontent <b>F</b>orgery is a [[vulnerability]] class that entails malforming the server-side mimetype for a particular resource to make it appear as something else. | ||
{{notice|This is by no means original, however the [[Facebook]] wiki documents [[Facebook#Proof_of_Concept|how to do this in detail]].}} | {{notice|This is by no means original, however the [[Facebook]] wiki documents [[Facebook#Proof_of_Concept|how to do this in detail]].}} | ||
| − | For example, | + | |
| + | For example, you could have an innocent looking image file hosted somewhere, using apache directives such as "AddType" you can force the content-type of the resource to be processed server-side by any application. | ||
| + | |||
| + | When the application seizes control of the resource, you can wrap that resource into the functions of a program, wherein the output would be returned to the client | ||
| + | |||
| + | This vulnerability is possible because content-crawler bots make easily identifiable requests. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | {{exploitation}} | ||
| + | {{social}} | ||
| + | |||
| + | [[Category:Web exploitation]] | ||
Latest revision as of 22:49, 15 May 2012
| This article contains too little information, it should be expanded or updated. |
|---|
Things you can do to help:
|
| It has been proposed that XSCF be merged with XSS. |
|---|
| If you have comments please make them on the Discussion page. |
Introduction
Cross-Site Content Forgery is a vulnerability class that entails malforming the server-side mimetype for a particular resource to make it appear as something else.
Notice: This is by no means original, however the Facebook wiki documents how to do this in detail.
For example, you could have an innocent looking image file hosted somewhere, using apache directives such as "AddType" you can force the content-type of the resource to be processed server-side by any application.
When the application seizes control of the resource, you can wrap that resource into the functions of a program, wherein the output would be returned to the client
This vulnerability is possible because content-crawler bots make easily identifiable requests.
