CVE-2013-4318 json
Features file injection vulnerability
published 6y ago modified 4mo ago also GHSA-42gq-h7xj-33r4 , EUVD-2022-2268
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
File injection vulnerability in Ruby gem Features 0.3.0 allows remote attackers to inject malicious html in the /tmp directory.
Is CVE-2013-4318 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.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- openwall.com http://www.openwall.com/lists/oss-security/2013/09/09/10 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | features | <=0.3.0 |
no fix listed |
Affected products
- Features Features
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
References
-
openwall.com
/lists/oss-security/2013/09/09/10
web, exploit, mailing-list, third-party-advisory
-
security-tracker.debian.org
/tracker/CVE-2013-4318
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2013-4318
advisory
-
github.com
/mhennemeyer/features
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/features/CVE-2013-4318.yml
web
Sources
- CVE List CVE-2013-4318
- GitHub Advisory GHSA-42gq-h7xj-33r4
- NVD CVE-2013-4318
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.