# CVE-2021-40825: Hardcoded credentials in n/a

> Remote attackers can exploit a default key to modify lighting conditions or update software on nLight ECLYPSE controllers.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pvm8-7672-fw3w

## What is CVE-2021-40825?

CVE-2021-40825 is a high-severity vulnerability in n/a, published on 17 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

nLight ECLYPSE (nECY) system Controllers running software prior to 1.17.21245.754 contain a default key vulnerability. The nECY does not force a change to the key upon the initial configuration of an affected device. nECY system controllers utilize an encrypted channel to secure SensorViewTM configuration and monitoring software and nECY to nECY communications. Impacted devices are at risk of exploitation. A remote attacker with IP access to an impacted device could submit lighting control commands to the nECY by leveraging the default key. A successful attack may result in the attacker gaining the ability to modify lighting conditions or gain the ability to update the software on lighting devices. The impacted key is referred to as the SensorView Password in the nECY nLight Explorer Interface and the Gateway Password in the SensorView application. An attacker cannot authenticate to or modify the configuration or software of the nECY system controller.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2021-40825?

It affects 1 product.


Products: Acuitybrands Nlight Eclypse System Controller Firmware.

## How do I fix CVE-2021-40825?

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

## Is CVE-2021-40825 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-40825 and fix it if it is affected.

What it is: CVE-2021-40825 is a high-severity vulnerability in n/a, published on 17 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-40825 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-2021-40825/ (Markdown: https://insights.sbomify.com/CVE-2021-40825/index.md)
```

## Sources

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

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