CVE-2014-4994 json
Gyazo allows local users to write arbitrary files
published 2018-01-10 8 y ago modified 2026-06-17 4 mo ago also GHSA-6x45-86q6-rcmr , EUVD-2018-0153
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
lib/gyazo/client.rb in the gyazo gem 1.0.0 for Ruby allows local users to write to arbitrary files via a symlink attack on a temporary file, related to time-based filenames.
Patch / fix
- rubygems gyazo 2.0.0
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- vapid.dhs.org http://www.vapid.dhs.org/advisories/gyazo-1.0.0.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | gyazo | >=1.0.0, <2.0.0 |
2.0.0 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
vapid.dhs.org
/advisories/gyazo-1.0.0.html
exploit, third-party-advisory
-
openwall.com
/lists/oss-security/2014/07/17/5
mailing-list, web, third-party-advisory
-
openwall.com
/lists/oss-security/2014/07/07/13
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2014-4994
advisory
-
github.com
/gyazo/gyazo-ruby
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/gyazo/CVE-2014-4994.yml
web
-
web.archive.org
/web/20200229061943/http://www.vapid.dhs.org/advisories/gyazo-1.0.0.html
web
Sources
- CVE List CVE-2014-4994
- GitHub Advisory GHSA-6x45-86q6-rcmr
- NVD CVE-2014-4994
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.