Application hang via retrying malformed requests
Published Apr 29, 2025 · Updated Apr 29, 2025
Improper HTTP handling in Snowflake Connector for C/C++ 0.5.0 through 2.1.0 allows local users to hang client applications. The connector's HTTP response handler classifies status code 400 from malformed requests as retryable and repeats the request up to SF_CON_MAX_RETRY times, seven by default. Exploitation requires local low-privileged access to cause a consuming application to issue a malformed request; the bounded impact is a hang until the retries finish.
Summary
What happened
Improper HTTP handling in Snowflake Connector for C/C++ 0.5.0 through 2.1.0 allows local users to hang client applications. The connector's HTTP response handler classifies status code 400 from malformed requests as retryable and repeats the request up to SF_CON_MAX_RETRY times, seven by default. Exploitation requires local low-privileged access to cause a consuming application to issue a malformed request; the bounded impact is a hang until the retries finish.
The record
- CVE
- CVE-2025-46330
- Published
- Apr 29, 2025
- Updated
- Apr 29, 2025
- Vendor
- Snowflake
- Product
- Snowflake Libsnowflakeclient
- Classifications
- CWE-573, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 2025CVE publishedPublication date reported by the CVE source.
- Apr 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.5.0, < 2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo