# CVE-2020-16134: Privilege escalation in n/a

> Attackers with local access or credentials can create privileged users on the Sysbus-API to gain superuser SSH access on Swisscom Internet Box devices.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w7f8-p623-gp6f

## What is CVE-2020-16134?

CVE-2020-16134 is a high-severity vulnerability in n/a, published on 4 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Swisscom Internet Box 2, Internet Box Standard, Internet Box Plus prior to 10.04.38, Internet Box 3 prior to 11.01.20, and Internet Box light prior to 08.06.06. Given the (user-configurable) credentials for the local Web interface or physical access to a device's plus or reset button, an attacker can create a user with elevated privileges on the Sysbus-API. This can then be used to modify local or remote SSH access, thus allowing a login session as the superuser.

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

It affects 5 products.


Products: Swisscom Internet-Box 2 Firmware, Swisscom Internet-Box 3 Firmware, Swisscom Internet-Box Light Firmware, Swisscom Internet-Box Plus Firmware, Swisscom Internet-Box Standard Firmware.

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

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

## Is CVE-2020-16134 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16596](https://insights.sbomify.com/CVE-2018-16596/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-16134 is a high-severity vulnerability in n/a, published on 4 Aug 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-16134 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-16134/ (Markdown: https://insights.sbomify.com/CVE-2020-16134/index.md)
```

## Sources

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

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