CVE-2013-2105 json
Script Injection in Show In Browser gem
published 12y ago modified 4mo ago also GHSA-9hx9-w2j6-rw76 , EUVD-2017-0206
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
The Show In Browser (show_in_browser) gem 0.0.3 for Ruby allows local users to inject arbitrary web script or HTML via a symlink attack on /tmp/browser.html.
Is CVE-2013-2105 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
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- openwall.com http://www.openwall.com/lists/oss-security/2013/05/18/4 referenced PoC, tagged "exploit" by a source, unverified
- vapid.dhs.org http://vapid.dhs.org/advisories/show_in_browser.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.3 | AV:L/AC:M/Au:N/C:N/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | show_in_browser | 1 listed version |
no fix listed |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
openwall.com
/lists/oss-security/2013/05/18/4
mailing-list, web, exploit
-
vapid.dhs.org
/advisories/show_in_browser.html
web, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/84378
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-2105
advisory
-
github.com
/jonleung/show_in_browser
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/show_in_browser/CVE-2013-2105.yml
web
Sources
- CVE List CVE-2013-2105
- GitHub Advisory GHSA-9hx9-w2j6-rw76
- NVD CVE-2013-2105
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.