# CVE-2013-4318: Features file injection vulnerability

> Remote attackers can inject malicious HTML into the /tmp directory via the Features Ruby gem, potentially leading to code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-42gq-h7xj-33r4

## What is CVE-2013-4318?

CVE-2013-4318 is a medium-severity cross-site scripting vulnerability in Features, published on 26 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

File injection vulnerability in Ruby gem Features 0.3.0 allows remote attackers to inject malicious html in the /tmp directory.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2013-4318?

2 open source packages ship an affected version, including features. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `features` | RubyGems | All versions to 0.3.0 | None |
| `features` | RubyGems | All versions to 0.3.0 | None |

Products: Feature Project Feature.

## How do I fix CVE-2013-4318?

No fix has been published for CVE-2013-4318 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4318 being exploited?

There is no known exploitation of CVE-2013-4318 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4318 and fix it if it is affected.

What it is: CVE-2013-4318 is a medium-severity cross-site scripting vulnerability in Features, published on 26 Dec 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-4318 in the wild and no public exploit code.

Affected packages and fixed versions:
- features (RubyGems): affected all versions up to 0.3.0; no fix listed
- features (RubyGems): affected all versions up to 0.3.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4318/ (Markdown: https://insights.sbomify.com/CVE-2013-4318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4318
- OSV: https://osv.dev/vulnerability/CVE-2013-4318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4318/
Summaries are generated and may contain mistakes; the official description above is the record.