Skip to content

snowflake-connector-python vulnerable to SQL Injection in write_pandas

High severity GitHub Reviewed Published Jan 29, 2025 in snowflakedb/snowflake-connector-python • Updated Jan 29, 2025

Package

pip snowflake-connector-python (pip)

Affected versions

>= 2.2.5, <= 3.13.0

Patched versions

3.13.1

Description

Issue

Snowflake discovered and remediated a vulnerability in the Snowflake Connector for Python. A function from the snowflake.connector.pandas_tools module is vulnerable to SQL injection.

This vulnerability affects versions 2.2.5 through 3.13.0. Snowflake fixed the issue in version 3.13.1.

Vulnerability Details

A function from the snowflake.connector.pandas_tools module is not sanitizing all of its arguments, and queries using them are not parametrized. An attacker controlling these arguments could achieve SQL injection by passing crafted input. Any SQL executed that way by an attacker would still run in the context of the current session.

Solution

Snowflake released version 3.13.1 of the Snowflake Connector for Python, which fixes this issue. We recommend users upgrade to version 3.13.1.

Additional Information

If you discover a security vulnerability in one of our products or websites, please report the issue to HackerOne. For more information, please see our Vulnerability Disclosure Policy.

References

@sfc-gh-fochnik sfc-gh-fochnik published to snowflakedb/snowflake-connector-python Jan 29, 2025
Published to the GitHub Advisory Database Jan 29, 2025
Reviewed Jan 29, 2025
Published by the National Vulnerability Database Jan 29, 2025
Last updated Jan 29, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

CVE ID

CVE-2025-24793

GHSA ID

GHSA-2vpq-fh52-j3wv

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.