medium CVSS 5.5

CVE-2024-49750·Python vulnerability

The Snowflake Connector for Python provides an interface for developing Python applications that can connect to Snowflake and perform all standard operations. Prior to version 3.12.3, when the logging level was set by the user to DEBUG, the Connector could have logged Duo passcodes (when specified via the `passcode` parameter) and Azure SAS tokens. Additionally, the SecretDetector logging formatter, if enabled, contained bugs which caused it to not fully redact JWT tokens and certain private key formats. Snowflake released version 3.12.3 of the Snowflake Connector for Python, which fixes the issue. In addition to upgrading, users should review their logs for any potentially sensitive information that may have been captured.

Severity
medium
Software
Python
Fixed in
3.12.3
Published
2024-10-24

Affected versions

Until: 3.12.3

Fixed in: 3.12.3

How to fix this CVE

Upgrade the Snowflake Connector for Python to version 3.12.3 or later to prevent accidental exposure of authentication credentials in debug logs. This vulnerability affects applications using DEBUG-level logging, which may inadvertently capture Duo passcodes, Azure SAS tokens, JWT tokens, and private keys. After upgrading, audit your existing log files for any sensitive data that may have been logged and securely rotate affected credentials.

sudo dnf upgrade python3-snowflake

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed Snowflake Connector version by running: python3 -c "import snowflake.connector; print(snowflake.connector.__version__)"
  2. Step 2: Verify if your application uses DEBUG-level logging by searching configuration files for 'DEBUG' or 'logging.DEBUG' in your Python codebase
  3. Step 3: Search application logs for patterns matching Duo passcode formats (typically 6-8 digits) and SAS tokens (containing 'sv=', 'ss=', 'sig=') by running: grep -i 'passcode\|sv=.*ss=' /var/log/application.log
  4. Step 4: After upgrading, confirm the new version is active by re-running the version check command and validating version 3.12.3 or higher is returned

FAQ

What is CVE-2024-49750?

CVE-2024-49750 is a credential disclosure vulnerability in Snowflake Connector for Python where DEBUG-level logging inadvertently exposes authentication secrets like Duo passcodes, Azure SAS tokens, and JWT tokens that should have been redacted.

Is CVE-2024-49750 being actively exploited?

No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and has no publicly available exploits. However, it poses risk if logs are accessible to unauthorized users.

What versions of Snowflake Connector for Python are affected by CVE-2024-49750?

All versions prior to 3.12.3 are affected. The vulnerability was introduced in earlier versions and patched in release 3.12.3.

How do I check if my server is vulnerable to CVE-2024-49750?

Run: python3 -c "import snowflake.connector; print(snowflake.connector.__version__)" and compare the output against version 3.12.3. If your version is below 3.12.3, you are vulnerable.

Does Defensia detect CVE-2024-49750?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Snowflake Connector for Python is installed on a monitored server, CVE-2024-49750 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-49750. Free for 1 server.

Get started free