CVE-2017-2096 json
smalruby and smalruby-editor vulnerable to OS Command Injection
published 2017-04-28 9 y ago modified 2026-06-17 4 mo ago also GHSA-f489-655r-x6gr , EUVD-2022-3682
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.2%
- EPSS 6.2% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
smalruby-editor v0.4.0 and earlier allows remote attackers to execute arbitrary OS commands via unspecified vectors.
Patch / fix
- rubygems smalruby-editor 0.4.1
- rubygems smalruby 0.1.11
Exploit prediction
6.18% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | smalruby-editor | <0.4.1 |
0.4.1 |
| rubygems | smalruby | <0.1.11 |
0.1.11 |
Affected products
- Ruby Programming Shounendan smalruby-editor
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
smalruby.jp
/blog/2017/01/14/smalruby-editor-0-4-1-has-been-released-english.html
web, release-notes, vendor-advisory
-
jvn.jp
/en/jp/JVN50197114/index.html
third-party-advisory, web, vdb-entry
-
securityfocus.com
/bid/95775
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-2096
advisory
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/smalruby/CVE-2017-2096.yml
web
-
github.com
/smalruby/smalruby-editor
package
-
web.archive.org
/web/20200227194312/http://www.securityfocus.com/bid/95775
web
Sources
- CVE List CVE-2017-2096
- GitHub Advisory GHSA-f489-655r-x6gr
- NVD CVE-2017-2096
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.