# CVE-2020-11925: Hardcoded credentials in n/a

> Attackers can gain root access to Luvion Grand Elite 3 devices using shared default credentials, compromising device security.

- **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:** 2 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-35j3-w22f-jh7w

## What is CVE-2020-11925?

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

### Official description

An issue was discovered in Luvion Grand Elite 3 Connect through 2020-02-25. Authentication to the device is based on a username and password. The root credentials are the same across all devices of this model.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Luvion Grand Elite 3 Connect Firmware.

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

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

## Is CVE-2020-11925 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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