CyberRota Analysis
AI-GeneratedThe vulnerability arises from the lack of a leading-dash validation check in the LaunchConfigurationBaseSerializer.scm_branch, which could allow for unsafe input to be processed. Although currently mitigated by a runtime check, this gap in API validation could potentially lead to remote code execution if the defense mechanism is removed. Organizations using affected products should prioritize addressing this issue to prevent exploitation through the API.
Original NVD Description
LaunchConfigurationBaseSerializer.scm_branch has no validate_scm_branch() leading-dash check, unlike Project/JobTemplate/JobLaunch serializers. Schedule and WFJT Node accept --upload-pack=/bin/id as scm_branch. Currently blocked at runtime by jobs.py:1502 ValueError check (defense-in-depth), but the API validation gap means sole reliance on a task-layer guard. Refactoring that guard away would promote this to RCE.