The vulnerability stems from multiple SaltStack modules that handled SSL/TLS connections without proper certificate validation. The SaltStack release notes explicitly list affected modules (asam runner, splunk returner, vsphere/esxi modules, bigip, panos proxy, etc.) and state they were patched to validate SSL by default. While exact function names aren't provided in advisory texts, these modules' core connection-handling functions (e.g., get_service_instance for vSphere, management_root for BIG-IP) would logically be responsible for SSL configuration. The high confidence comes from Salt's own documentation of the CVE fixes directly linking these modules to the vulnerability.