Security readout for executives and security teams
Plain-English summary
Libre Wireless LS9 LS1.5/p7040 devices can disclose the device configuration password to anyone who can reach the affected service. This is a credential exposure issue, not merely an information banner leak, because the password is returned in cleartext without authentication.
Executive priority
Prioritize any exposed devices because this flaw can reveal configuration credentials without login. If devices are isolated from untrusted networks, urgency is lower but remediation should still be tracked.
Technical view
The luci_service daemon on port 7777 lacks authentication for a password-retrieval function and can return the device configuration password in cleartext. The source bundle does not provide CVSS, CWE, patch status, or detailed affected CPE data.
Likely exposure
Exposure is limited to Libre Wireless LS9 LS1.5/p7040 devices where port 7777 is reachable by an untrusted network path. Internet, guest Wi-Fi, or flat internal network reachability would raise urgency.
Exploitation context
The CVE record describes unauthenticated password disclosure, but the bundle does not cite active exploitation and the CVE is not marked KEV. Treat exploit status as unknown, with risk driven by service reachability.
Researcher notes
The public data is sparse: no CVSS, CWE, CPE, or patch details are included. The core issue is clear credential disclosure from luci_service, but validation should focus on asset confirmation and network reachability.
Mitigation direction
- Identify Libre Wireless LS9 LS1.5/p7040 devices in the environment.
- Restrict untrusted access to port 7777 and device management networks.
- Check vendor or advisory guidance for firmware updates or supported fixes.
- Rotate device configuration passwords after exposure is removed.
- Monitor for unexpected access to the affected management service.
Validation and detection
- Confirm whether any LS9 LS1.5/p7040 devices are deployed.
- Verify port 7777 is not reachable from untrusted networks.
- Review firewall, VLAN, and Wi-Fi segmentation around these devices.
- Check asset records for firmware or remediation status.
- Look for historical access to the affected service.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
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 lookupCVE-2020-35756 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.iot-inspector.com/blog/advisory-multiple-issues-libre-wireless-ls9/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.