Awesome CVE PoC

repository·master·Indexed 26 days ago

https://github.com/qazbnm456/awesome-cve-poc

A curated collection of Proof of Concept (PoC) exploits and technical details for various Common Vulnerabilities and Exposures (CVEs). The repository provides links to exploit demonstrations, GitHub repositories, blog posts, and Gists for vulnerabilities ranging from 2011 to 2020, covering browsers (Chrome, WebKit, IE), operating systems (Windows, Linux), and software such as Apache, Samba, and ActiveMQ.

Tokens
46.4K
Snippets
94
Records
552
Agent score
86%

What's inside awesome-cve-poc

  1. Overview of Awesome CVE PoC

    master
    Awesome CVE PoC is a curated collection of Proof of Concepts (PoCs) for Common Vulnerabilities and Exposures (CVEs). It serves as a resource for security researchers and developers to find exploit demonstrations for known vulnerabilities.
  2. Access CVE Proof-of-Concept (PoC) Resources

    master
    This repository serves as a collection of links to Proof-of-Concept (PoC) exploits and technical details for various Common Vulnerabilities and Exposures (CVEs). Users can browse the list to find specific vulnerabilities related to browsers (Chrome, WebKit, IE), operating systems (Windows, Linux), and software (Apache, Samba, ActiveMQ, etc.). Each entry typically provides a link to a GitHub repository, a blog post, a Gist, or an exploit database containing the exploit code or detailed analysis.
  3. Browse CVE Proof of Concept (PoC) repository contents

    master
    The awesome-cve-poc repository contains a curated list of Proof of Concept (PoC) implementations for various Common Vulnerabilities and Exposures (CVEs). You can navigate the repository to find specific PoC code for vulnerabilities ranging from 2011 to 2020. Each entry in the table of contents links to a dedicated section or file containing the exploit or demonstration code for that specific CVE.
  4. Exploit CVE-2017-9993: Local File Disclosure via ffmpeg

    master

    CVE-2017-9993 is a vulnerability in FFmpeg that allows for Local File Disclosure. An attacker can exploit this to read arbitrary files from the local system by leveraging specific FFmpeg processing capabilities.

    Detailed exploitation steps and technical details can be found in the linked HackerOne report.

  5. Access Proof of Concept (PoC) for CVE-2017-1000353

    master

    Proof of Concept (PoC) implementations for the CVE-2017-1000353 Jenkins Java Deserialization vulnerability can be found in the following repositories:

    • nixawk/labs: Contains lab environments for testing.
    • phith0n/vulhub: Provides a Vulhub environment specifically for this Jenkins vulnerability.
    https://github.com/nixawk/labs/tree/master/CVE-2017-1000353
    https://github.com/phith0n/vulhub/tree/master/jenkins/CVE-2017-1000353
  6. Reproduce CVE-2017-12611 (S2-053)

    master

    To reproduce the CVE-2017-12611 (also known as S2-053) vulnerability, you can use the following resources:

    1. Analysis and PoC: A detailed reproduction analysis process and PoC are available via the TuiSec paper link.
    2. Vulnerable Application: Use the s2-053 directory within the Medicean/VulApps repository to set up a controlled environment for testing this Struts2 vulnerability.
    https://github.com/Medicean/VulApps/tree/master/s/struts2/s2-053
  7. Access Proof of Concept (PoC) implementations for CVE-2017-5754

    master

    To test for or demonstrate the CVE-2017-5754 (Meltdown) rogue data cache load vulnerability, you can use the following external PoC repositories and implementations:

    • IAIK/meltdown: A repository containing Meltdown exploit code.
    • CacheAttack.cpp: A C++ implementation available via Pastebin.
    • paboldin/meltdown-exploit: An exploit repository for Meltdown.
    • raphaelsc/Am-I-affected-by-Meltdown: A tool to check if a system is vulnerable to Meltdown.
    • lgeek/spec_poc_arm: A speculative execution PoC specifically for ARM architectures.
    • GitMirar/meltdown-poc: Another implementation of the Meltdown PoC.
  8. Mitigate AWS AMI loading risks

    master
    When using the AWS CLI to describe images, always specify the --owners flag. Failing to do so may result in unintentionally loading undesired or potentially malicious Amazon Machine Images (AMIs) from the uncurated public community catalog instead of validated sources.
  9. Configure Apache Tomcat CGI Servlet security

    master

    On Windows, the Apache Tomcat CGI Servlet is vulnerable to Remote Code Execution (RCE) if enableCmdLineArguments is enabled.

    • Vulnerable versions: Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39, and 7.0.0 to 7.0.93.
    • Default behavior: The CGI option enableCmdLineArguments is disabled by default. In Tomcat 9.0.x, it is disabled by default and will remain so in response to this vulnerability.
  10. Secure Apache Solr DataImportHandler (DIH)

    master

    In Apache Solr version 8.2.0 and later, the dataConfig parameter in the DataImportHandler (DIH) admin screen is a security risk because it can contain scripts. To use this parameter, you must explicitly enable it by setting the following Java System property to true:

    enable.dih.dataConfigParam