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

> Remote attackers can execute arbitrary code by deploying and accessing a malicious service in IBM SPSS Analytical Decision Management.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-979x-3prm-92mq

## What is CVE-2013-5369?

CVE-2013-5369 is a critical code injection vulnerability in n/a, published on 16 Sep 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM SPSS Analytical Decision Management 6.1 before IF1, 6.2 before IF1, and 7.0 before FP1 IF6 might allow remote attackers to execute arbitrary code by deploying and accessing a service.

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

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

It affects 1 product.


Products: Ibm Spss Analytical Decision Management.

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

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

## Is CVE-2013-5369 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4049](https://insights.sbomify.com/CVE-2013-4049/): File upload in n/a (high 8.5)
- [CVE-2013-4047](https://insights.sbomify.com/CVE-2013-4047/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-4048](https://insights.sbomify.com/CVE-2013-4048/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5369 is a critical code injection vulnerability in n/a, published on 16 Sep 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-5369 in the wild and no public exploit code.

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

## Sources

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

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