CVE-2022-42965 is a low-severity (CVSS 3.7) CWE-1333 vulnerability in snowflake-connector-python. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for snowflake-connector-python — see the affected versions and patch details below.
Exponential ReDoS in snowflake-connector-python leads to denial of service
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-42965.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
snowflake-connector-pythonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the snowflake-connector-python PyPI package, when an attacker is able to supply arbitrary input to the undocumented get_file_transfer_type method
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | snowflake-connector-python | all versions | 2.8.2pip install --upgrade 'snowflake-connector-python==2.8.2' |
Affected Products
snowflake connectorsnowflakeResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snowflake-connector-python, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update snowflake-connector-python to 2.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-42965 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2022-42965 in your dependencies?
Find it across PyPI, including transitive dependencies.