# CVE-2020-15809: Server-side request forgery in n/a

> Attackers can exploit SSRF and path traversal in SpinetiX media players to access unintended internal resources and sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 24 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-25qv-rf35-39r8

## What is CVE-2020-15809?

CVE-2020-15809 is a medium-severity server-side request forgery vulnerability in n/a, published on 24 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

spxmanage on certain SpinetiX devices allows requests that access unintended resources because of SSRF and Path Traversal. This affects HMP350, HMP300, and DiVA through 4.5.2-1.0.36229; HMP400 and HMP400W through 4.5.2-1.0.2-1eb2ffbd; and DSOS through 4.5.2-1.0.2-1eb2ffbd.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2020-15809?

It affects 6 products.


Products: Spinetix Diva Firmware, Spinetix Dsos, Spinetix Hmp300 Firmware, Spinetix Hmp350 Firmware, Spinetix Hmp400 Firmware, Spinetix Hmp400w Firmware.

## How do I fix CVE-2020-15809?

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

## Is CVE-2020-15809 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15809 and fix it if it is affected.

What it is: CVE-2020-15809 is a medium-severity server-side request forgery vulnerability in n/a, published on 24 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15809 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-2020-15809/ (Markdown: https://insights.sbomify.com/CVE-2020-15809/index.md)
```

## Sources

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

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