-
Notifications
You must be signed in to change notification settings - Fork 51
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
Keys flagged but don't seem to work #158
Comments
Are you getting the same result every time, or did it only happen once? |
I wouldn't necessarily assume BlackList3r is going to get it, there was definitely a few edge cases I got working that they didn't account for |
Same results every time. Weirdly it seems that when badsecrets flags but blacklist3r does not it means the way to exploit it is a different badsecrets only is |
Does your last comment imply that you got it to work? Is the viewstate you posted unmodified? I can't seem to get a detection working just from that. Also, were you using it in URL mode or manually supplying the viewstate and generator? In general, I'd say exploitation can be tricky sometimes. I still run into situations where some tiny little detail makes things not work. However, so far, I have never seen a single true false positive from badsecrets. I am sure there have been a few false negatives. |
I was using url mode and i'll try get a list of sites it's flagged on but blacklist3r has not to see if there is a common output that i'm missing that should be obvious on why blacklist3r isn't seeing them but badsecrets is. |
Hey,
During a test
i got these come back...
Tried to exploit the site for the client but wasn't able to.
Threw the keys in to blacklist3r (ASP version) to confirm it can decode them and got this. Which i'm thinking is this a false positive as the original blacklist3r should be able to decode the viewstate if the keys are correct.
The text was updated successfully, but these errors were encountered: