# CVE-2020-17405: Deserialization in Symphony

> Network-adjacent attackers can execute arbitrary code with SYSTEM privileges via unsafe deserialization in the SSOAuth process.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-39c2-x5w3-56xm

## What is CVE-2020-17405?

CVE-2020-17405 is a high-severity unsafe deserialization vulnerability in Senstar Symphony, published on 1 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Senstar Symphony 7.3.2.2. Authentication is not required to exploit this vulnerability. The specific flaw exists within the SSOAuth process. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-10980.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Senstar Symphony.

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

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

## Is CVE-2020-17405 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-17405 is a high-severity unsafe deserialization vulnerability in Senstar Symphony, published on 1 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-17405 in the wild and no public exploit code.

Affected product: Senstar Symphony. 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-17405/ (Markdown: https://insights.sbomify.com/CVE-2020-17405/index.md)
```

## Sources

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

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