CVE-2025-59042

一、漏洞信息
 漏洞编号：[CVE-2025-59042](https://nvd.nist.gov/vuln/detail/CVE-2025-59042)
 漏洞归属组件：[python-pyinstaller](https://gitee.com/src-openeuler/python-pyinstaller)
 漏洞归属的版本：3.6,5.13.0
 CVSS V3.0分值：
  BaseScore：N/A None
  Vector：CVSS：3.0/
 漏洞简述：
  PyInstaller bundles a Python application and all its dependencies into a single package. Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller < 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met. First, the application is built with PyInstaller < 6.0.0; both onedir and onefile mode are affected. Second, the optional bytecode encryption code feature was not enabled during the application build. Third, the attacker can create files/directories in the same directory where the executable is located. Fourth, the filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems). Fifth, the attacker is able to determine the offset at which the PYZ archive is embedded in the executable. The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in the absence of the real, built-in module that is available when the bytecode-encryption feature is enabled). This results in arbitrary code execution that requires no modification of the executable itself. If the executable is running with elevated privileges (for example, due to having the `setuid` bit set), the code in the injected module is also executed with the said elevated privileges, resulting in a local privilege escalation. PyInstaller 6.0.0 (f5adf291c8b832d5aff7632844f7e3ddf7ad4923) removed support for bytecode encryption; this effectively removes the described attack vector, due to the bootstrap script not attempting to load the optional module for bytecode-decryption anymore. PyInstaller 6.10.0 (cfd60b510f95f92cb81fc42735c399bb781a4739) reworked the bootstrap process to avoid (ab)using `sys.path` for transmitting location of the PYZ archive, which further eliminates the possibility of described injection procedure. If upgrading PyInstaller is not feasible, this issue can be worked around by ensuring proper permissions on directories containing security-sensitive executables (i.e., executables with `setuid` bit set) should mitigate the issue.
 漏洞公开时间：2025-09-10 07:15:37
 漏洞创建时间：2025-09-10 02:01:41
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-59042
<details>
<summary>更多参考(点击展开)</summary>

无
</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  七彩瞬析开源风险感知平台
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

无
</details>

二、漏洞分析结构反馈
 影响性分析说明：
  PyInstaller bundles a Python application and all its dependencies into a single package. Due to a special entry being appended to sys.path during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in sys.path, an application built with PyInstaller < 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when all of the following conditions are met. First, the application is built with PyInstaller < 6.0.0; both onedir and onefile mode are affected. Second, the optional bytecode encryption code feature was not enabled during the application build. Third, the attacker can create files/directories in the same directory where the executable is located. Fourth, the filesystem supports creation of files/directories that contain ? in their name (i.e., non-Windows systems). Fifth, the attacker is able to determine the offset at which the PYZ archive is embedded in the executable. The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in the absence of the real, built-in module that is available when the bytecode-encryption feature is enabled). This results in arbitrary code execution that requires no modification of the executable itself. If the executable is running with elevated privileges (for example, due to having the setuid bit set), the code in the injected module is also executed with the said elevated privileges, resulting in a local privilege escalation. PyInstaller 6.0.0 (f5adf291c8b832d5aff7632844f7e3ddf7ad4923) removed support for bytecode encryption; this effectively removes the described attack vector, due to the bootstrap script not attempting to load the optional module for bytecode-decryption anymore. PyInstaller 6.10.0 (cfd60b510f95f92cb81fc42735c399bb781a4739) reworked the bootstrap process to avoid (ab)using sys.path for transmitting location of the PYZ archive, which further eliminates the possibility of described injection procedure. If upgrading PyInstaller is not feasible, this issue can be worked around by ensuring proper permissions on directories containing security-sensitive executables (i.e., executables with setuid bit set) should mitigate the issue.
 openEuler评分：
  7.3
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-22.03-LTS-SP3(3.6):受影响
2.openEuler-22.03-LTS-SP4(3.6):受影响
3.openEuler-24.03-LTS(5.13.0):受影响
4.openEuler-24.03-LTS-Next(5.13.0):受影响
5.openEuler-24.03-LTS-SP1(5.13.0):受影响
6.openEuler-24.03-LTS-SP2(5.13.0):受影响
7.master(6.15.0):不受影响
8.openEuler-20.03-LTS-SP4:不受影响

修复是否涉及abi变化(是/否)：
  1.master(6.15.0):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3(3.6):否
4.openEuler-22.03-LTS-SP4(3.6):否
5.openEuler-24.03-LTS(5.13.0):否
6.openEuler-24.03-LTS-Next(5.13.0):否
7.openEuler-24.03-LTS-SP1(5.13.0):否
8.openEuler-24.03-LTS-SP2(5.13.0):否

原因说明：
  1.openEuler-24.03-LTS(5.13.0):正常修复
2.openEuler-24.03-LTS-Next(5.13.0):正常修复
3.openEuler-24.03-LTS-SP1(5.13.0):正常修复
4.openEuler-24.03-LTS-SP2(5.13.0):正常修复
5.openEuler-22.03-LTS-SP3(3.6):暂不修复-待升级版本修复
6.openEuler-22.03-LTS-SP4(3.6):暂不修复-待升级版本修复
7.openEuler-20.03-LTS-SP4:不受影响-组件不存在
8.master(6.15.0):不受影响-漏洞代码不能被攻击者触发

src-openEuler/python-pyinstaller

Content Risk Flag

Comments (13)

src-openEuler/python-pyinstaller .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2025-59042

Comments (13)

Search

src-openEuler/python-pyinstaller