The vulnerability stems from insecure HTTP URLs hardcoded in configuration objects (seleniumserver, chromedriver, iedriver) within lib/config.js. These URLs were used to download executables. While the URLs are part of the module's configuration data rather than traditional functions, the insecure protocol made the system vulnerable. The fix changed these static URL strings from 'http' to 'https', but no specific functions (e.g., download handlers or URL builders) were identified in the provided diff—only configuration properties were modified. Thus, no functions meet the criteria for inclusion with high confidence.