Nuclei Path Traversal vulnerability
cve-program · CVE-2023-37896
PublishedNuclei 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.
Read the publisher's advisoryeuvd · EUVD-2023-2189
PublishedNuclei 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.
Read the publisher's advisorynvd · CVE-2023-37896
PublishedNuclei 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.
Read the publisher's advisoryosv · GHSA-2xx4-jj5v-6mff
Published## Overview We have identified and addressed a security issue in the Nuclei project that 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 payloads loading in `sandbox` mode. ## Details In the previous versions, 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 the latest release, v2.9.9. We 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 disabled by default and `-lna` (restrict local network access) which can be optionally disabled by user. The `-lfa` allows file (payload) access anywhere on the system (disabling sandbox effectively), and `-lna` blocks connections to the local/private network. ## Affected Versions This issue affected all versions of Nuclei prior to v2.9.9. ## Patches We recommend all users upgrade to the latest version, [v2.9.9](https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.9), which includes the security fix. ### References - [patch](https://github.com/projectdiscovery/nuclei/pull/3927) - [releases](https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.9) ## Acknowledgments We would like to thank **keomutchoiboi** who reported this issue to us via our security email, [[email protected]](mailto:[email protected]). We appreciate the responsible disclosure of this issue.
Read the publisher's advisoryosv · GO-2023-1998
PublishedImproper path sanitization in sandbox mode in github.com/projectdiscovery/nuclei/v2
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-37896 · CVE overview and exploitation status
cve-program · CVE-2023-37896
- https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-2xx4-jj5v-6mff
- https://github.com/projectdiscovery/nuclei/pull/3927
- https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.9
euvd · EUVD-2023-2189
- https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-2xx4-jj5v-6mff
- https://github.com/projectdiscovery/nuclei/pull/3927
- https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.9
nvd · CVE-2023-37896
- https://github.com/projectdiscovery/nuclei/pull/3927
- https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.9
- https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-2xx4-jj5v-6mff
osv · GHSA-2xx4-jj5v-6mff
- https://github.com/projectdiscovery/nuclei/security/advisories/GHSA-2xx4-jj5v-6mff
- https://nvd.nist.gov/vuln/detail/CVE-2023-37896
- https://github.com/projectdiscovery/nuclei/pull/3927
- https://github.com/projectdiscovery/nuclei
- https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.9
osv · GO-2023-1998
Related changes
Linked by CVE identifierNo related changes are available here.