CVE-2013-2516 json
Fileutils Command Injection vulnerability
published 7y ago modified 4mo ago also GHSA-9x97-x2p9-hvpf , EUVD-2022-3463
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Vulnerability in FileUtils v0.7, Ruby Gem Fileutils <= v0.7 Command Injection vulnerability in user supplied url variable that is passed to the shell.
Patch / fix
Is CVE-2013-2516 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
3.33% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- vapidlabs.com http://www.vapidlabs.com/advisory.php?v=36 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | fileutils | <0.7.1 |
0.7.1 |
Affected products
- Stefaan Colman FileUtils
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
-
github.com
/ruby/fileutils/commit/994c7aa1ba391689f844a069b9aee9e49813686c
web
-
vapidlabs.com
/advisory.php?v=36
web, exploit, third-party-advisory
-
rubygems.org
/gems/fileutils
web, product, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2013-2516
advisory
-
bugs.ruby-lang.org
/issues/7958
web
-
github.com
/ruby/fileutils
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/fileutils/CVE-2013-2516.yml
web
Sources
- CVE List CVE-2013-2516
- GitHub Advisory GHSA-9x97-x2p9-hvpf
- NVD CVE-2013-2516
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.