CyberRota Analysis
AI-GeneratedThe Snowflake JDBC Driver versions 4.2.0 through 4.3.3 are vulnerable due to improper input validation of the auto-configuration account identifier, allowing attackers to redirect credential-bearing login requests to malicious HTTPS endpoints. This could enable an attacker to capture and reuse login credentials, potentially granting them unauthorized access to sensitive resources. Organizations utilizing these specific driver versions should prioritize upgrading to version 4.3.4 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Improper input validation of the auto-configuration account identifier in Snowflake JDBC Driver versions 4.2.0 through 4.3.3 allowed a credential-bearing login request to be redirected to an attacker-selected HTTPS endpoint. An attacker able to control the account value could cause the driver to transmit a reusable login credential to a host of their choosing and replay it to obtain the privileges granted to that credential. Successful exploitation requires an application using jdbc:snowflake:auto with a connections.toml section that omits an explicit host and a lower-trust principal able to set the account value; ordinary JDBC URLs are unaffected. The fix is available in Snowflake JDBC Driver version 4.3.4, including the snowflake-jdbc-fips and snowflake-jdbc-thin. Users must manually upgrade.