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

ticketbleed reporting is not correct #595

hansgoes opened this Issue Oct 27, 2017 · 0 comments


None yet
1 participant

hansgoes commented Oct 27, 2017

in the json output ticketbleed also reports 1 which means NOT vurnerable but seccubus says vurnerable.

@seccubus seccubus closed this in 0fab7cc Nov 1, 2017

seccubus added a commit that referenced this issue Nov 1, 2017

Merge pull request #596 from schubergphilis/595-ticketbleed
FIxed #595 - Incorrect parsing of the values for Ticketbleed finding …
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment