Security readout for executives and security teams
Plain-English summary
Libre Wireless LS9 LS1.5/p7040 devices may show a login page but still allow unauthenticated users to reach privileged web-interface APIs. If the device management interface is reachable by untrusted users, this can undermine administrative access controls and expose internal device functions.
Executive priority
Treat this as urgent for any reachable device management interface. Prioritize isolation and vendor guidance checks before normal change windows if exposure extends beyond a tightly controlled admin network.
Technical view
CVE-2020-35758 is an authentication bypass in the LS9 web interface. The reported issue is improper restriction of internal functionality, allowing direct access to APIs that should require authentication. Public data does not provide CVSS, CWE, CPE, fixed versions, or patch status.
Likely exposure
Exposure is most likely where Libre Wireless LS9 LS1.5/p7040 device web interfaces are reachable from user networks, partner networks, or the internet. The source bundle does not prove internet-scale exposure.
Exploitation context
The CVE is not listed as CISA KEV in the supplied bundle. The cited description supports unauthenticated access to privileged APIs, but no active exploitation, public exploit use, or attacker campaign is cited.
Researcher notes
The public record is sparse: no CVSS, CWE, CPE, affected version range, fixed version, or remediation detail is supplied. Analysis should focus on asset confirmation, reachability, and whether privileged API access is actually gated by authentication.
Mitigation direction
- Inventory Libre Wireless LS9 LS1.5/p7040 devices and management interfaces.
- Restrict web-interface access to trusted administrative networks only.
- Check Libre Wireless or advisory guidance for firmware updates or official mitigations.
- Segment affected devices if no confirmed fix is available.
- Monitor management-interface traffic for unexpected unauthenticated API access.
Validation and detection
- Confirm whether LS9 LS1.5/p7040 devices exist in the environment.
- Identify all networks that can reach each device web interface.
- Verify management access requires authentication before privileged API functionality is exposed.
- Review device logs and network telemetry for suspicious web-interface requests.
- Document firmware versions and compare them with vendor or advisory guidance.
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-35758 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.
