Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I’d like to suggest adding Jiraffe to the offensive tools section.
I’ve been using Jiraffe for Jira security work for a while now, and it recently went through a big refactor that made it significantly cleaner and more reliable. It’s a Jira-focused scanner that helps identify misconfigurations, unauthenticated access, and validate known Jira CVEs, with practical SSRF helpers that are especially useful in cloud-hosted Jira deployments (including metadata targets).
It feels similar in spirit to tools like TruffleHog, but for Atlassian Jira.
Thought it might be a good fit for the list. Thanks for maintaining this repo.