# CVE-2013-5036: Code injection in n/a

> Remote attackers can execute arbitrary code via crafted YAML documents in the Square Squash web application.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jjmf-p64f-6wmv

## What is CVE-2013-5036?

CVE-2013-5036 is a high-severity code injection vulnerability in n/a, published on 27 May 2014. It can be exploited over the network, with no action from the victim.

### Official description

The Square Squash allows remote attackers to execute arbitrary code via a YAML document in the (1) namespace parameter to the deobfuscation function or (2) sourcemap parameter to the sourcemap function in app/controllers/api/v1_controller.rb.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Squash Square Squash.

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

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

## Is CVE-2013-5036 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5036 exists.

Public exploit code:

- Squash YAML Code Execution (metasploit)
- Squash - YAML Code Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5036 is a high-severity code injection vulnerability in n/a, published on 27 May 2014. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5036 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-5036/ (Markdown: https://insights.sbomify.com/CVE-2013-5036/index.md)
```

## Sources

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

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