Sensitive information written to logs by Snowflake drivers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Snowflake | Snowflake Connector for Python | unaffected |
|
||||||
| Snowflake | Snowflake Go Driver | unaffected |
|
||||||
| Snowflake | Snowflake Go Driver | unaffected |
|
||||||
| Snowflake | Snowflake JDBC Driver | unaffected |
|
||||||
| Snowflake | Snowflake JDBC Driver (FIPS) | unaffected |
|
||||||
| Snowflake | Snowflake JDBC Driver (Thin) | unaffected |
|
||||||
| Snowflake | Snowflake Node.js Driver | unaffected |
|
||||||
| Snowflake | Snowflake PHP PDO Driver | unaffected |
|
||||||
| Snowflake | Snowflake ODBC Driver | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Snowflake | Snowflake-connector-python |
|
||||||||
| Snowflake | Snowflake Go Driver |
|
||||||||
| Snowflake | Snowflake Jdbc Driver |
|
||||||||
| Snowflake | Snowflake Node.js Driver |
|
||||||||
| Snowflake | Snowflake Odbc Driver |
|
||||||||
| Snowflake | Snowflake Php Pdo Driver |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-qqj6-54q6-cxv6 | Snowflake drivers writes sensitive information to logs |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.089% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Insertion of sensitive information into log files in the Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers allowed authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions to be written to diagnostic logs in circumstances where the available log redaction did not cover all affected log paths and data types. An attacker with read access to the log destination, whether the local filesystem, a log aggregation service, or a CI/CD artifact store, could obtain credentials and decryption keys that, if still valid at the time of access, could be used to authenticate to the corresponding Snowflake account or cloud-storage object. Successful exploitation requires read access to the log destination, and impact is bounded by credential lifetime and object scope. The fix is available in the patched versions listed above. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required. | Insertion of sensitive information into log files in the Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers allowed authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions to be written to diagnostic logs in circumstances where the available log redaction did not cover all affected log paths and data types. An attacker with read access to the log destination, whether the local filesystem, a log aggregation service, or a CI/CD artifact store, could obtain credentials and decryption keys that, if still valid at the time of access, could be used to authenticate to the corresponding Snowflake account or cloud-storage object. Successful exploitation requires read access to the log destination, and impact is bounded by credential lifetime and object scope. The fix is available in Snowflake Connector for Python v4.7.3, Snowflake Go Driver v2.2.0, Snowflake JDBC Driver v4.3.4 (including the snowflake-jdbc-fips and snowflake-jdbc-thin), Snowflake Node.js Driver v3.3.0, Snowflake PHP PDO Driver v4.2.0, and Snowflake ODBC Driver v3.20.0. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required. |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Snowflake
Snowflake snowflake-connector-python Snowflake snowflake Go Driver Snowflake snowflake Jdbc Driver Snowflake snowflake Node.js Driver Snowflake snowflake Odbc Driver Snowflake snowflake Php Pdo Driver |
|
| Vendors & Products |
Snowflake
Snowflake snowflake-connector-python Snowflake snowflake Go Driver Snowflake snowflake Jdbc Driver Snowflake snowflake Node.js Driver Snowflake snowflake Odbc Driver Snowflake snowflake Php Pdo Driver |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Insertion of sensitive information into log files in the Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers allowed authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions to be written to diagnostic logs in circumstances where the available log redaction did not cover all affected log paths and data types. An attacker with read access to the log destination, whether the local filesystem, a log aggregation service, or a CI/CD artifact store, could obtain credentials and decryption keys that, if still valid at the time of access, could be used to authenticate to the corresponding Snowflake account or cloud-storage object. Successful exploitation requires read access to the log destination, and impact is bounded by credential lifetime and object scope. The fix is available in the patched versions listed above. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required. | |
| Title | Sensitive information written to logs by Snowflake drivers | |
| Weaknesses | CWE-532 | |
| References |
|
|
| Metrics |
cvssV3_1
|