Git-Vuln-Finder - Finding Potential Software Vulnerabilities From Git Commit Messages


[![](https://1.bp.blogspot.com/-juT5vi-pFfM/XhUxVfCayLI/AAAAAAAARXU/sjfoo0DpvVgPdrkk4Mq1833ughr7O5cgwCNcBGAsYHQ/s1600/git-vuln-finder.png)](<https://1.bp.blogspot.com/-juT5vi-pFfM/XhUxVfCayLI/AAAAAAAARXU/sjfoo0DpvVgPdrkk4Mq1833ughr7O5cgwCNcBGAsYHQ/s1600/git-vuln-finder.png>) Finding potential software [vulnerabilities](<https://www.kitploit.com/search/label/vulnerabilities> "vulnerabilities" ) from git commit messages. The output format is a JSON with the associated commit which could contain a fix regarding a software vulnerability. The search is based on a set of [regular expressions](<https://www.kitploit.com/search/label/Regular%20Expressions> "regular expressions" ) against the commit messages only. If CVE IDs are present, those are added automatically in the output. **Requirements** * Python 3.6 * GitPython * langdetect **Usage** usage: finder.py [-h] [-v] [-r R] [-o O] [-s S] [-p P] [-c] [-t] Finding potential software vulnerabilities from git commit messages. optional arguments: -h, --help show this help message and exit -v increase output verbosity -r R git repository to analyse -o O Output format: [json] -s S State of the commit found -p P Matching pattern to use: [vulnpatterns, cryptopatterns, cpatterns] - the pattern 'all' is used to match all the patterns at once. -c output only a list of the CVE pattern found in commit messages (disable by default) -t Include tags matching a specific commit More info: https://github.com/cve-search/git-vuln-finder **Patterns** git-vuln-finder comes with 3 default patterns which can be selected to find the potential vulnerabilities described in the commit messages such as: * `vulnpatterns` is a generic [vulnerability](<https://www.kitploit.com/search/label/Vulnerability> "vulnerability" ) pattern especially targeting web application and generic security commit message. Based on an academic paper. * `cryptopatterns` is a vulnerability pattern for cryptographic errors mentioned in commit messages. * `cpatterns` is a set of standard vulnerability patterns see for C/C++-like languages. **A sample partial output from Curl git repository** python3 finder.py -r /home/adulau/git/curl | jq . ... "6df916d751e72fc9a1febc07bb59c4ddd886c043": { "message": "loadlibrary: Only load system DLLs from the system directory\n\nInspiration provided by: Daniel Stenberg and Ray Satiro\n\nBug: https://curl.haxx.se/docs/adv_20160530.html\n\nRef: Windows DLL [hijacking](<https://www.kitploit.com/search/label/Hijacking> "hijacking" ) with curl, CVE-2016-4802\n", "language": "en", "commit-id": "6df916d751e72fc9a1febc07bb59c4ddd886c043", "summary": "loadlibrary: Only load system DLLs from the system directory", "stats": { "insertions": 180, "deletions": 8, "lines": 188, "files": 7 }, "author": "Steve Holme", "author-email": "some-email@example.com", "authored_date": 1464555460, "committed_date": 1464588867, "branches": [ "master" ], "pa ttern-selected": "(?i)(denial of service |\bXXE\b|remote code execution|\bopen redirect|OSVDB|\bvuln|\bCVE\b |\bXSS\b|\bReDoS\b|\bNVD\b|malicious|x−frame−options|attack|cross site |exploit|malicious|directory traversal |\bRCE\b|\bdos\b|\bXSRF \b|\bXSS\b|clickjack|session.fixation|hijack|\badvisory|\binsecure |security |\bcross−origin\b|unauthori[z|s]ed |infinite loop)", "pattern-matches": [ "hijack" ], "origin": "some-email@example.com:curl/curl.git", "origin-github-api": "https://api.github.com/repos/curl/curl/commits/6df916d751e72fc9a1febc07bb59c4ddd886c043", "tags": [], "cve": [ "CVE-2016-4802" ], "state": "cve-assigned" }, "c2b3f264cb5210f82bdc84a3b89250a611b68dd3": { "message": "CONNECT_ONLY: don't close connection on GSS 401/407 reponses\n\nPreviously, connections were closed immediately before the user had a\nchance to extract the socket when the proxy required Ne gotiate\nauthentication.\n\nThis regression was brought in with the security fix in commit\n79b9d5f1a42578f\n\nCloses #655\n", "language": "en", "commit-id": "c2b3f264cb5210f82bdc84a3b89250a611b68dd3", "summary": "CONNECT_ONLY: don't close connection on GSS 401/407 reponses", "stats": { "insertions": 4, "deletions": 2, "lines": 6, "files": 1 }, "author": "Marcel Raad", "author-email": "some-email@example.com", "authored_date": 1455523116, "committed_date": 1461704516, "branches": [ "master" ], "pattern-selected": "(?i)(denial of service |\bXXE\b|remote code execution|\bopen redirect|OSVDB|\bvuln|\bCVE\b |\bXSS\b|\bReDoS\b|\bNVD\b|malicious|x−frame−options|attack|cross site |exploit|malicious|directory traversal |\bRCE\b|\bdos\b|\bXSRF \b|\bXSS\b|clickjack|session.fixation|hijack|\badvisory|\binsecure |security |\bcross−origi n\b|unauthori[z|s]ed |infinite loop)", "pattern-matches": [ "security " ], "origin": "some-email@example.com:curl/curl.git", "origin-github-api": "https://api.github.com/repos/curl/curl/commits/c2b3f264cb5210f82bdc84a3b89250a611b68dd3", "tags": [], "state": "under-review" }, ... * Extracting CVE id(s) from git messages "98d132cf6a879faf0147aa83ea0c07ff326260ed": { "message": "Add a macro for testing assertion in both debug and production builds\n\nIf we have an assert then in a debug build we want an abort() to occur.\nIn a production build we wan t the function to return an error.\n\nThis introduces a new macro to assist with that. The idea is to replace\nexisting use of OPENSSL_assert() with this new macro. The problem with\nOPENSSL _assert() is that it aborts() on an assertion failure in both debug\nand production builds. It should never be a library's decision to abort a\nprocess (we don't get to decide when to kill t he life support machine or\nthe nuclear reactor control system). Additionally if an attacker can\ncause a reachable assert to be hit then this can be a source of DoS attacks\ne.g. see CVE-20 17-3733, CVE-2015-0293, CVE-2011-4577 and CVE-2002-1568.\n\nReviewed-by: Tim Hudson <some-email@example.com>\n(Merged from https://github.com/openssl/o penssl/pull/3496)", "commit-id": "98d132cf6a879faf0147aa83ea0c07ff326260ed", "summary": "Add a macro for testing assertion in both debug and production builds", "stats": { "insertions": 18, "deletions": 0, "lines": 18, "files": 1 }, "author": "Matt Caswell", "author-email": "some-email@example.com", "authored_date": 1495182637, "committed_date": 1495457671, "branches": [ "master" ], "pattern-selected": "(?i)(denial of service |\bXXE\b|remote code execution|\bopen redirect|OSVDB|\bvuln|\bCVE\b |\bXSS\b|\bReDoS\b|\bNVD\b|malicious|x−frame−options|attack|cross site |ex ploit|malicious|directory traversal |\bRCE\b|\bdos\b|\bXSRF \b|\bXSS\b|clickjack|session.fixation|hijack|\badvisory|\binsecure |security |\bcross−origin\b|unauthori[z|s]ed |infinite loop)", "pattern-matches": [ "attack" ], "cve": [ "CVE-2017-3733", "CVE-2015-0293", "CVE-2011-4577", "CVE-2002-1568" ], "state": "cve-assigned" } **Acknowledgment** * Thanks to [Jean-Louis Huynen](<https://github.com/gallypette> "Jean-Louis Huynen" ) for the discussions about the crypto vulnerability pattern * Thanks to [Sebastien Tricaud](<https://github.com/stricaud> "Sebastien Tricaud" ) for the discussions regarding native language and commit messages **References** * [Notes](<https://gist.github.com/adulau/dce5a6ca5c65017869bb01dfee576303#file-finding-vuln-git-commit-messages-md> "Notes" ) * <https://csce.ucmss.com/cr/books/2017/LFS/CSREA2017/ICA2077.pdf> (mainly using CVE referenced in the commit message) - archive (<http://archive.is/xep9o>) * <https://asankhaya.github.io/pdf/automated-identification-of-security-issues-from-commit-messages-and-bug-reports.pdf> (2 main regexps) **[Download Git-Vuln-Finder](<https://github.com/cve-search/git-vuln-finder> "Download Git-Vuln-Finder" )**