The vulnerability stems from improper template processing in Hive/Presto engines. Engine-specific template processors exposed: 1) The current database connection object with plaintext credentials 2) User password hashes 3) Metadata database contents. These functions likely provided a Jinja context with dangerous variables/objects, allowing authenticated users to access sensitive data through SQL template injection (e.g., {{ current_connection.password }}). The high confidence comes from the vulnerability's specific mention of template field exploitation and connection object method execution, which would require these engine-specific template processors to be the attack surface.