diff --git a/.DS_Store b/.DS_Store deleted file mode 100644 index c3569931fd..0000000000 Binary files a/.DS_Store and /dev/null differ diff --git a/README.md b/README.md index 443d94e643..00768cb50e 100644 --- a/README.md +++ b/README.md @@ -1,69 +1,23 @@ -
](https://trickest.io/auth/register)
-
-## How it works
-### [Trickest](https://trickest.com) Workflow Architecture
-
-
-
-### TB; DZ (Too big; didn't zoom):
-- Collect CVE details from [cvelist](https://github.com/CVEProject/cvelist) (Shout out to [CVE Project](https://github.com/CVEProject)!)
-- Split CVEs up by year.
-- Find PoCs for each CVE using 2 techniques:
- 1. References
- - Gather each CVE's `References`.
- - Check if any of them points to a PoC using [ffuf](https://github.com/ffuf/ffuf) and a list of keywords
-
- Regex:
- ```(?i)[^a-z0-9]+(poc|proof of concept|proof[-_]of[-_]concept)[^a-z0-9]+```
-
- (Thanks [@joohoi](https://github.com/joohoi)!)
-
- **Note**: [ffuf](https://github.com/ffuf/ffuf) is awesome for more purposes than just content discovery.
-
- Get CVE referenced in HackerOne Reports - [AllVideoPocsFromHackerOne](https://github.com/zeroc00I/AllVideoPocsFromHackerOne) (Thanks [@zeroc00I](https://github.com/zeroc00I)!)
-
-
- 2. Github
-
- Search GitHub for repositories with [find-gh-poc](https://github.com/trickest/find-gh-poc) that mention the CVE ID.
-- Merge the fresh results into the repository without overwriting the data that was committed manually.
-- Filter false positives using `blacklist.txt`.
-- Merge all of the found PoCs.
-- Generate GitHub badges for each affected software version using [shields.io](https://shields.io).
-- Write everything into easy-to-read markdown files.
-
-
-
-> **As described, almost everything in this repository is generated automatically. We carefully designed the workflow (and continue to develop it) to ensure the results are as accurate as possible.**
-
-
-
## Use cases
- Browse around, find a nice PoC, and test away!
- `Watch` the repository to receive notifications about new PoCs as soon as they go public.
- Search for a specific product(s) (and possibly version) to find all public exploits related to it.
-- Monitor the [atom feed](https://github.com/trickest/cve/commits/main.atom) for a specific product(s).
+- Monitor the [atom feed](https://github.com/0xMarcio/cve/commits/main.atom) for a specific product(s).
- Create a searchable HTML table using the template and script in [summary_html](summary_html)
- - Example: https://www.andrewmohawk.com/cve_summary (Thanks [@AndrewMohawk](https://github.com/AndrewMohawk)!)
## Contribution
-All contribtutions/ideas/suggestions are welcome! Create a new ticket via [GitHub issues](https://github.com/trickest/cve/issues) or tweet at us [@trick3st](https://twitter.com/trick3st).
-
-## Build your own workflows
-
-We believe in the value of tinkering; cookie-cutter solutions rarely cut it. Sign up for a [Trickest](https://trickest.com) demo to customize this workflow to your use case, get access to many more workflows, or build your own workflows from scratch!
-
-[
](https://trickest.io/auth/register)
+All contribtutions/ideas/suggestions are welcome! Create a new ticket via [GitHub issues](https://github.com/0xMarcio/cve/issues) .
\ No newline at end of file