Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-j8g2-6fc7-q8f8
No affected components available
Impact
This impacts users of Python 3.11 that are using a Pyramid static view with a full filesystem path and have a index.html file that is located exactly one directory above the location of the static view's file system path. No further path traversal exists, and the only file that could be disclosed accidentally is index.html.
Example:
config.add_static_view(name='static', path='/usr/src/app/static', cache_max_age=0)
And directory tree:
/usr/src/app \
| - static \
| - file.css
| - index.html
| - ...
| - index.html <-- (this file could be disclosed with this bug)
Patches
Pyramid now will reject any path that contains a null-byte out of caution. While valid in directory/file names, we would strongly consider it a mistake to use null-bytes in naming files/directories.
Secondly, Python 3.11, and 3.12 has fixed the underlying issue in os.path.normpath to no longer truncate on the first 0x00 found, returning the behavior to pre-3.11 Python, un an as of yet unreleased version, see:
- https://github.com/python/cpython/issues/106242
- https://github.com/python/cpython/pull/106816
At the time the following Python versions are not fixed:
- Python 3.11.0 to 3.11.4
- Python 3.12.0a1 to 3.12.0rc1
Fixes will be available in: Python 3.12.0rc2 or 3.11.5.
Please note that release candidates of Python are not production ready and should not be used for production workloads.
Workarounds
Use a version of Python 3 that is not affected. Downgrade to Python 3.10 series temporarily, or wait till Python 3.11.5 is released and upgrade to the latest version of Python 3.11 series.
References
- https://owasp.org/www-community/attacks/Path_Traversal
- VN: JVN#41113329
- TN: JPCERT#93311166
Thanks
- Masashi Yamane of LAC Co., Ltd
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard