github.com/projectdiscovery/nuclei/v2
Affected
- introduced
0, fixed2.9.9(semver)
Fixed versions
2.9.9
Fix
- Fixed version
2.9.9go get github.com/projectdiscovery/nuclei/[email protected]
Advisory
Also known as: CVE-2023-37896, GO-2023-1998
Nuclei Path Traversal vulnerability
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, which includes the security fix.
References
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.
High Basis: The source's own band: HIGH
0, fixed 2.9.9 (semver)2.9.9
2.9.9go get github.com/projectdiscovery/nuclei/[email protected]0, fixed 2.9.9 (semver)2.9.9
2.9.9go get github.com/projectdiscovery/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0