Nuclei Path Traversal vulnerability
projectdiscovery nuclei
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectdiscovery/nuclei/v2 Go |
|
|
| github.com/projectdiscovery/nuclei Go |
|
|
projectdiscovery nuclei
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectdiscovery/nuclei/v2 Go |
|
|
| github.com/projectdiscovery/nuclei Go |
|
|
Nuclei is a vulnerability scanner. Prior to version 2.9.9, a security issue in the Nuclei project affected users utilizing Nuclei as Go code (SDK) running custom templates. This issue did not affect CLI users. The problem was related to sanitization issues with payload loading in sandbox mode. There was a potential risk with payloads loading in sandbox mode. The issue occurred due to relative paths not being converted to absolute paths before doing the check for `sandbox` flag allowing arbitrary files to be read on the filesystem in certain cases when using Nuclei from `Go` SDK implementation.
This issue has been fixed in version 2.9.9. The maintainers have also enabled sandbox by default for filesystem loading. This can be optionally disabled if required. The `-sandbox` option has been deprecated and is now divided into two new options: `-lfa` (allow local file access) which is enabled by default and `-lna` (restrict local network access) which can be enabled by users optionally. The `-lfa` allows file (payload) access anywhere on the system (disabling sandbox effectively), and `-lna` blocks connections to the local/private network.
From the CVE record · GitHub_M
Before 2.9.9, Nuclei’s Go SDK could fail to enforce sandbox checks when loading payloads from relative paths in custom templates. This could allow arbitrary filesystem files to be read in certain cases. CLI users were not affected; the input does not specify attacker access or authentication requirements.
Check applications using github.com/projectdiscovery/nuclei/v2 or github.com/projectdiscovery/nuclei versions before 2.9.9 as a Go SDK with custom templates.