CyberRota Analysis
AI-GeneratedIncorrect path-string matching in the configuration of SingularityCE and SingularityPRO allows unauthorized containers to be executed from sibling directories, potentially bypassing security restrictions set by the administrator. This vulnerability primarily affects installations using the limit container paths directive, which could lead to unauthorized access and execution of malicious containers. Organizations utilizing these container platforms should prioritize patching to versions 4.4.2 or later for SingularityCE and 4.3.9 or 4.1.14 for SingularityPRO to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when /data/safe is allowed under setuid mode. This permits a user to run a container from outside the administrator's configured path allowlist. Installations that do not use limit container paths are not affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14.