CVE-2021-3779 — ruby-mysql
MEDIUMCVE-2021-3779 is a medium-severity (CVSS 6.5) CWE-610 vulnerability in ruby-mysql. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for ruby-mysql — see the affected versions and patch details below.
Externally Controlled Reference to a Resource in Another Sphere in ruby-mysql
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
ruby-mysqlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
A malicious actor can read arbitrary files from a client that uses ruby-mysql to communicate to a rogue MySQL server and issue database queries. In these cases, the server has the option to create a database reply using the LOAD DATA LOCAL statement, which instructs the client to provide additional data from a local file readable by the client (and not a "local" file on the server).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | ruby-mysql | all versions | 2.10.0bundle update ruby-mysql --conservative |
Affected Products
ruby-mysqlruby-mysql_projectResearch 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 ruby-mysql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ruby-mysql to 2.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3779 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2021-3779 in your dependencies?
Find it across RubyGems, including transitive dependencies.