Skip to content
#

cve

Here are 378 public repositories matching this topic...

有关渗透测试的POC、EXP、脚本、提权、小工具等---About penetration-testing python-script poc getshell csrf xss cms php-getshell domainmod-xss penetration-testing-poc csrf-webshell cobub-razor cve rce sql sql-poc poc-exp bypass oa-getshell cve-cms

  • Updated Apr 6, 2021
  • PowerShell

Guidance for the Spectre, Meltdown, Speculative Store Bypass, Rogue System Register Read, Lazy FP State Restore, Bounds Check Bypass Store, TLBleed, and L1TF/Foreshadow vulnerabilities as well as general hardware and firmware security guidance. #nsacyber

  • Updated Mar 16, 2021
  • C
terriko
terriko commented Mar 31, 2021

Many of our checkers have a shebang line that looks like #!/usr/bin/python3 in them just below the copyright/licensing info. Normally, this line occurs at the top of python files as helpers for when they're used as shell scripts. Since checkers are generally not used as shell scripts (they can't even run by themselves) there's no reason to keep this line there. It doesn't hurt anything and it

Improve this page

Add a description, image, and links to the cve topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the cve topic, visit your repo's landing page and select "manage topics."

Learn more