# CVE-2020-9473: Auth bypass in n/a

> An attacker with network access can exploit a passwordless SSH user to gain root access on the Siedle Smart Gateway.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2020
- **Updated:** 4 Aug 2024

## What is CVE-2020-9473?

CVE-2020-9473 is a medium-severity authentication bypass vulnerability in n/a, published on 6 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The S. Siedle & Soehne SG 150-0 Smart Gateway before 1.2.4 has a passwordless ftp ssh user. By using an exploit chain, an attacker with access to the network can get root access on the gateway.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Siedle Sg 150-0 Firmware.

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

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

## Is CVE-2020-9473 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9474](https://insights.sbomify.com/CVE-2020-9474/): File upload in n/a (high 8.8)
- [CVE-2020-9475](https://insights.sbomify.com/CVE-2020-9475/): Race condition in n/a (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9473 is a medium-severity authentication bypass vulnerability in n/a, published on 6 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9473 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-9473/ (Markdown: https://insights.sbomify.com/CVE-2020-9473/index.md)
```

## Sources

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

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