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

Feature: Use wildcard to indicate injection points that aren't standard GET parameters. #19

Closed
Macmod opened this issue Feb 14, 2017 · 3 comments

Comments

@Macmod
Copy link

Macmod commented Feb 14, 2017

Similarly to sqlmap, a wildcard could be used to indicate injection points that aren't standard GET parameters.

@epinna
Copy link
Owner

epinna commented Feb 14, 2017

Wildcard in POST request data and headers is already supported.

POST data

$ ./tplmap.py -u 'http://localhost:15001/post/mako' --data 'var=ok&inj=*&othervar=1'

Headers

$ ./tplmap.py -u 'http://localhost:15001/header/mako' --headers 'User-Agent: *' --headers 'X-Agent: *'

You can run it against the test python suite.

$ cd tests
$ ./run_python_tests.sh

@epinna epinna closed this as completed Feb 14, 2017
@Macmod
Copy link
Author

Macmod commented Feb 15, 2017

Thanks for clarifying, epinna, and the question should be elaborated: is there currently a way to do that in the URL, but outside GET parameters? That's the support I meant to ask for.

If my injection point is, for instance, http://www.example.com/HERE or http://www.example.com/dir/dir/dir/HERE, urlparse.parse_qs will return an empty dictionary and no injection will be tested. This may seem odd, but it's a real scenario considering mod_rewrite rules.

@epinna
Copy link
Owner

epinna commented Feb 15, 2017

Got you. Injection points in the URL are not yet supported, but I'll work on that.

@epinna epinna reopened this Feb 15, 2017
@epinna epinna changed the title Feature: Parse nonstandard injection points in the URL with wildcards. Feature: Use wildcard to indicate injection points that aren't standard GET parameters. Mar 7, 2017
@epinna epinna closed this as completed in f9a83e0 Mar 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants