Questions about this topic? Sign up to ask in the talk tab.

Difference between revisions of "XSCF"

From NetSec
Jump to: navigation, search
m (Changed protection level for "XSCF" ([edit=sysop] (indefinite) [move=sysop] (indefinite) [read=sysop] (indefinite)))
 
(5 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, let's say you have an image sitting somewhere that looks innocent.  Using Apache directives such as AddType, you can force the content-type of the resource to be processed server-side by any program.  The program then seizes control of the resource, and you can then wrap the resource into the functions of the program that is being executed to return output to the client.  This is possible because different sites and crawler bots make easily identifiable requests.
+
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.
  
{{series
+
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
| Name = XSCF
+
 
| PartOf = Web Exploitation
+
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:
  • add more content.
  • update current content.
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.



XSCF is part of a series on exploitation.
<center>
</center>