CVE-2023-30535
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSnowflake JDBC provides a JDBC type 4 driver that supports core functionality, allowing Java program to connect to Snowflake. Users of the Snowflake JDBC driver were vulnerable to a command injection vulnerability. An attacker could set up a malicious, publicly accessible server which responds to the SSO URL with an attack payload. If the attacker then tricked a user into visiting the maliciously crafted connection URL, the user’s local machine would render the malicious payload, leading to a remote code execution. The vulnerability was patched on March 17, 2023 as part of Snowflake JDBC driver Version 3.13.29. All users should immediately upgrade the Snowflake JDBC driver to the latest version: 3.13.29.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Snowflake JDBC driver versions before 3.13.29 contain a command injection vulnerability in SSO URL handling. An attacker can set up a malicious server that responds to SSO URL requests with an attack payload. When a user connects using a crafted URL pointing to this malicious server, the payload renders on the user's local machine, leading to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.13.29CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Snowflake JDBC driver versionLocate the snowflake-jdbc JAR file in your classpath or project dependencies. Check the file name for the version (e.g., snowflake-jdbc-3.13.28.jar) or inspect the MANIFEST.MF file inside the JAR for the Implementation-Version attribute. If using Maven, run 'mvn dependency:list' or check your pom.xml for the snowflake-jdbc artifact version.Affected if The installed version is lower than 3.13.29 (for example, 3.13.28, 3.13.0, or any version in the 3.13.x series before 3.13.29)
-
Verify if SSO authentication is configuredSearch your application configuration files, connection strings, or code for Snowflake connection parameters that enable SSO. Look for parameters such as 'authenticator=oauth', 'authenticator=okta', 'authenticator=azuread', 'authenticator=google', or any external IdP URL. Also check for the 'authenticator' parameter set to any value other than 'username_password' or 'internal'.Affected if SSO-based authentication (OAuth, Okta, Azure AD, Google, or other external IdP) is configured for Snowflake connections
-
Inspect SSO URL sourcesReview the authenticator URL or SSO endpoint configuration in your Snowflake connection setup. Determine whether the URL points to a trusted IdP or is dynamically constructed from user input, configuration files, or external sources. Check connection property files, environment variables, or code that builds the connection URL.Affected if The SSO authenticator URL is sourced from untrusted input, external configuration, or points to a non-standard IdP endpoint that could be controlled by an attacker
You are affected if your environment has Snowflake JDBC driver version below 3.13.29 AND uses SSO authentication with an IdP URL that could be malicious or controlled by an attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.13.29
Upgrade the Snowflake JDBC driver to version 3.13.29 or later to remediate this vulnerability.
Snowflake JDBC driver version 3.13.29
- Identify the current Snowflake JDBC driver version in use by checking project dependencies (e.g., pom.xml for Maven, build.gradle for Gradle, or JAR file version)
- Update the Snowflake JDBC driver dependency to version 3.13.29 or later. For Maven, update the pom.xml dependency to: <groupId>net.snowflake</groupId><artifactId>snowflake-jdbc</artifactId><version>3.13.29</version>
- For Gradle, update build.gradle to: implementation 'net.snowflake:snowflake-jdbc:3.13.29'
- If using a JAR file directly, replace the existing snowflake-jdbc JAR with version 3.13.29 or newer
- Verify the upgrade was successful by confirming the loaded driver version matches 3.13.29 or later
- Rebuild and redeploy the application to ensure the new driver is used in all environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30535 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data