The vulnerability arises from SparkSubmit's handling of the classpath in cluster mode when a proxy user is specified. The commit diff shows added checks in prepareSubmitEnvironment to clear childClasspath if proxy user is present and custom classpath is disallowed. Prior to this fix, the function did not perform these checks, allowing attackers to inject malicious classes via the classpath. The addition of the 'isCustomClasspathInClusterModeDisallowed' check and subsequent classpath clearing indicates that the prepareSubmitEnvironment function was the point where unsafe classpath entries were permitted, making it the vulnerable function.