CVE-2021-33473 json
Arbitrary file write in dragonfly
published 4y ago modified 4mo ago also GHSA-fj34-jhjx-xmvv , EUVD-2022-6037
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
An argument injection vulnerability in Dragonfly Ruby Gem v1.3.0 allows attackers to read and write arbitrary files when the verify_url option is disabled. This vulnerability is exploited via a crafted URL.
Patch / fix
Is CVE-2021-33473 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 4.9 | AV:N/AC:M/Au:S/C:P/I:P/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | dragonfly | <1.4.0 |
1.4.0 |
Classification
- Weakness
-
- CWE-88 Improper Neutralization of Argument Delimiters in a Command
References
-
github.com
/markevans/dragonfly/commit/25399297bb457f7fcf8e3f91e85945b255b111b5
web, patch, third-party-advisory
-
github.com
/markevans/dragonfly/issues/513
web, issue-tracking, third-party-advisory
-
security.netapp.com
/advisory/ntap-20220715-0004/
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-33473
advisory
-
github.com
/markevans/dragonfly
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/dragonfly/CVE-2021-33473.yml
web
-
security.netapp.com
/advisory/ntap-20220715-0004
web
Sources
- CVE List CVE-2021-33473
- GitHub Advisory GHSA-fj34-jhjx-xmvv
- NVD CVE-2021-33473
Fencer Intel 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.