trickest/find-gh-poc

Find CVE PoCs on GitHub

find-gh-poc's Issues

Update readme for public release

Read query from a file

read github-token from file

We should add also that GITHUB_TOKEN could be read from file input so it doesn't stay in .bash_history or similar, and the workflow itself doesn't contain it in any of the outputs,stdout or stderr

Add output file parameter

Query string has multiple whitespaces instead of one

Example when multiple queries were called recursively:

Keep only one whitespace to avoid potential errors related to query length when there is a huge number of results to be returned.

duplicated gihub poc urls

Some CVE file names have underscores instead of hyphens

Create separate files for all CVEs

Save all repos that reference a CVE in a file named CVE-yyyy-ID.txt

CVE files contain unrelated repositories

For example, in file CVE-2010-3971.txt:

• https://github.com/nektra/CVE-2010-3971-hotpatch
• https://github.com/LAITRUNGMINHDUC/CVE-2010-3600-PythonHackOracle11gR2
• https://github.com/mk219533/CVE-2010-1205
• https://github.com/aforakjackson/cve2010-2333
• https://github.com/n0lann/CVE2010-3301_compiled

Also, in file CVE-2020-0688.txt:

• https://github.com/ann0906/proxylogon

Note: Query that's been used is CVE-2010

1000 limit message shown for less than 1000 results

Discovered while testing #5

Bypass 1000 results limit on Github

Extract CVEs from README file and repo topics