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

Search for non-spec parameters #30

Closed
aph3rson opened this issue Sep 5, 2018 · 3 comments
Closed

Search for non-spec parameters #30

aph3rson opened this issue Sep 5, 2018 · 3 comments

Comments

@aph3rson
Copy link

aph3rson commented Sep 5, 2018

Per the SAML specification, any exchanged SAML payload should be in a parameter named SAMLRequest or SAMLResponse. However, developers occasionally don't follow spec, and use a differently-named parameter. This makes attempting SAML attacks with SAMLRaider difficult.

It would be desirable to have a feature where the target parameter (or a list thereof) could be customized. That way, if an application is out-of-spec, the list of potential parameters could be modified accordingly.

@emanuelduss
Copy link
Member

Hello

Thanks for your input. I have not seen that so far but I believe you that this could be done sometimes. I'll consider that configuration option in a future release. But I can't tell you when I will work the next time on SAML Raider.

However, if you need this now, a quick fix / hack / workaround could be to use two Burp instances behind each other (one Burp instance is the upstream proxy of the other). The first will then perform a search/replace for SAMLRequest/SAMLResponse to the custom parameter name and vice-versa. I have not tried it but this should work somehow.

Best regards,
Emanuel

@emanuelduss
Copy link
Member

Implemented in #49. Will be available in the next version.

@emanuelduss
Copy link
Member

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