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

> An attacker on the same network can bypass authentication on DIGITUS network hubs by sending a web-administration request without a password parameter.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 7 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fjx8-7rjg-vfv7

## What is CVE-2020-15063?

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

### Official description

DIGITUS DA-70254 4-Port Gigabit Network Hub 2.073.000.E0008 devices allow an attacker on the same network to bypass authentication via a web-administration request that lacks a password parameter.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Digitus Da-70254 Firmware.

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

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

## Is CVE-2020-15063 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15062](https://insights.sbomify.com/CVE-2020-15062/): Information disclosure in n/a (high 8.8)
- [CVE-2020-15065](https://insights.sbomify.com/CVE-2020-15065/): Denial of service in n/a (medium 6.5)
- [CVE-2020-15064](https://insights.sbomify.com/CVE-2020-15064/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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