github.com/projectdiscovery/nuclei/v2 v2.9.15
PkgFire would install this release with a warning.·Checked 4 hours ago·Published 16 September 2023
Why
-
warnVulnerability
Nuclei allows unsigned code template execution through workflows in github.com/projectdiscovery/nuclei
-
warnVulnerability
projectdiscovery/nuclei allows unsigned code template execution through workflows in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei Template Signature Verification Bypass in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Local File Read via require() Module Loader Bypass in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Environment variable disclosure via Response-Derived DSL Expressions in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Arbitrary Command Execution via DAST Code Signature Bypass in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Environment Variable Disclosure via Response-Derived Data in DAST/Fuzz Mode in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Local File Read via Workflow File-Protocol Gate Bypass in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability in github.com/projectdiscovery/nuclei
-
warnVulnerability
Nuclei: Local File Read via MySQL Client Sandbox Bypass in github.com/projectdiscovery/nuclei
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Source patterns
Patterns found in the source, including those malware is known to use.
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.