CVE-2021-3779 json
Ruby-MySQL Gem Client File Read
published 2022-06-28 4 y ago modified 2026-06-17 4 mo ago also GHSA-73pr-g6jj-5hc9 , EUVD-2022-5970
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
A malicious MySQL server can request local file content from a client using ruby-mysql prior to version 2.10.0 without explicit authorization from the user. This issue was resolved in version 2.10.0 and later.
Patch / fix
- rubygems ruby-mysql 2.10.0
- ruby-mysql_project ruby-mysql 2.10.0
Exploit prediction
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- rapid7.com https://www.rapid7.com/blog/post/2022/06/28/cve-2021-3779-ruby-mysql-gem-client-file-read-fixed/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | ruby-mysql | <2.10.0 |
2.10.0 |
Affected products
- Tomita Masahiro ruby-mysql
Classification
- Weakness
-
- CWE-610 Externally Controlled Reference to a Resource in Another Sphere
References
-
rapid7.com
/blog/post/2022/06/28/cve-2021-3779-ruby-mysql-gem-client-file-read-fixed/
exploit, mitigation, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-3779
advisory
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/ruby-mysql/CVE-2021-3779.yml
web
-
rapid7.com
/blog/post/2022/06/28/cve-2021-3779-ruby-mysql-gem-client-file-read-fixed
web
-
github.com
/tmtm/ruby-mysql
package
Sources
- CVE List CVE-2021-3779
- GitHub Advisory GHSA-73pr-g6jj-5hc9
- NVD CVE-2021-3779
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.