Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a demo!! #1

Closed
rajeshmajumdar opened this issue Aug 20, 2016 · 1 comment
Closed

Need a demo!! #1

rajeshmajumdar opened this issue Aug 20, 2016 · 1 comment

Comments

@rajeshmajumdar
Copy link

Hi there!! I am mew in XXE. I just want to know what should I put in that req.txt file Captured HTTP Requests or anything else.

@enjoiz
Copy link
Owner

enjoiz commented Aug 20, 2016

Hello,

Request file is just valid HTTP request with XML somewhere (parameter,
whole body, etc.). If XML is already in the request file then tool
automatically detects it and injects DTD to exploit vulnerability. You can
also specify XXEINJECT mark where DTD should be injected and tool will
replace it with proper payload. If you want to manually put DTD in request
file and you do not want to automatically detect and inject payload then
you need to specify --nodtd argument. Please note that if you put DTD
manually then it needs to be specified correctly. You can run tool with
--dtd argument to see how DTD should look like.

Sample request file where tool injects payload automatically:

POST /xxe.php HTTP/1.1
Host: asd

xml=

Sample request file where tool will inject DTD in specified place:

POST /xxe.php HTTP/1.1
Host: asd

xml=XXEINJECT

Sample request file with payload manually injected according to --dtd. You
need to specify --nodtd as parameter to disable automatic payload injection:

POST /xxe.php HTTP/1.1
Host: asd

xml=%remote;%int;%trick;]>

regards
JP

2016-08-20 20:33 GMT+02:00 Rajesh Majumdar notifications@github.com:

Hi there!! I am mew in XXE. I just want to know what should I put in that
req.txt file Captured HTTP Requests or anything else.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AL5OYPSfoszB0aqzF6e66RFCwGPDRT0hks5qh0higaJpZM4JpIm7
.

@enjoiz enjoiz closed this as completed Jan 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants