LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40825: nLight ECLYPSE (nECY) system Controllers running software prior to 1.17.21245.754 contain a default key vul...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects nLight ECLYPSE nECY lighting controllers before software 1.17.21245.754. A default key can remain unchanged after setup. Someone with network access to an affected controller could send lighting control commands or update lighting devices, disrupting building lighting operations.

Executive priority

Treat this as a facilities and operational resilience issue. It is not described as full controller compromise, but unauthorized lighting changes or lighting-device updates could disrupt occupants, safety procedures, or building operations.

Technical view

The nECY uses an encrypted channel for SensorView configuration, monitoring, and nECY-to-nECY communications. The device does not force replacement of the default SensorView/Gateway Password key during initial configuration. A remote attacker with IP access could leverage that default key to issue lighting commands, but sources say they cannot authenticate to or modify the nECY controller configuration or software.

Likely exposure

Exposure is most likely in facilities using nLight ECLYPSE nECY system controllers running software earlier than 1.17.21245.754, especially where controller management networks are reachable by untrusted users or broader corporate networks.

Exploitation context

The sources describe remote exploitation requiring IP access to an impacted device. CISA KEV status is false in the bundle, and no provided source states active exploitation or public exploit availability.

Researcher notes

Evidence is limited to the CVE record and vendor references in the bundle. No CVSS, CWE, detailed affected CPEs, or confirmed exploitation are provided. Scope validation should focus on nECY software version, default key state, and IP reachability.

Mitigation direction

  • Identify all nLight ECLYPSE nECY controllers and recorded software versions.
  • Update affected controllers to software 1.17.21245.754 or later where applicable.
  • Review vendor guidance for default SensorView/Gateway Password handling.
  • Restrict IP access to nECY management and lighting-control networks.
  • Monitor for unexpected lighting-control changes or device software updates.

Validation and detection

  • Confirm whether any nECY controller runs software earlier than 1.17.21245.754.
  • Verify the SensorView Password/Gateway Password is not left at default.
  • Check network paths that can reach nECY controller IP addresses.
  • Review logs or operational records for unauthorized lighting changes.
  • Document controller versions, network segmentation, and remediation status.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-40825 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.