Finding the bug was easier than figuring out which versions were actually vulnerable
Source Reddit Cybersecurity
Discussion
This content discusses the challenge of accurately determining vulnerable software versions for a given bug. The author created an open source CLI tool called Taggity to automate checking vulnerability descriptions against source code across software releases. The tool helped identify discrepancies in advisories, such as versions incorrectly marked as safe despite lacking fixes. The post is a link to the tool's GitHub repository and does not describe a specific vulnerability or exploit.
r/cybersecurity (opens in a new tab)u/VoidEqualZero0 points0 comments
I kept hitting this during vulnerability research when I’d find the bug, then spend hours jumping between tags to work out the affected range.
So I tried turning the vulnerability description into a source code check and running it across releases.
It caught an interesting case in qutebrowser where one advisory implied 11 releases were safe even though the fix wasn’t present in them.
I turned the workflow into an open source CLI called Taggity. Describe the vulnerability, review the drafted check, then test it against any version or audit an advisory’s claimed range.
Repo: https://github.com/nickelsec/taggity
If you have an advisory with a messy or disputed version range, send it over. I need harder cases :)