dbcve.org
L Switch And L Ip FirmwareOperating system · Loytec

CVE-2015-7906

HIGH · 10.0 CVSS v2.0 Published 2015-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LOYTEC LIP-3ECTB 6.0.1, LINX-100, LVIS-3E100, and LIP-ME201 devices allow remote attackers to read a password-hash backup file via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

LOYTEC building automation devices (LIP-3ECTB 6.0.1, LINX-100, LVIS-3E201, LIP-ME201) contain an information disclosure vulnerability allowing unauthenticated remote attackers to read password-hash backup files via unspecified vectors. The CVSS 10 score indicates network-exploitable with no authentication required, likely involving path traversal or improper access controls exposing sensitive authentication material.

MitigationIsolate affected devices behind a firewall with strict access controls, apply any available firmware updates from LOYTEC, and rotate all passwords after patching since the password hashes are compromised.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
L Switch And L Ip FirmwareOperating system
Affected:= 6.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LOYTEC device on the network
    Scan for devices running LOYTEC web interface (typically TCP ports 80/443) or check device fingerprints via SNMP community strings 'public'/'private'. Look for HTTP server banners containing 'LOYTEC' or 'LIP-' in responses.
    Affected if The device is a LOYTEC building automation controller (LIP-3ECTB, LINX-100, LVIS-3E201, LIP-ME201) visible on the network.
  2. Verify firmware version is 6.0.1
    Access the LOYTEC web interface (HTTP/HTTPS) and navigate to 'Device Info' or 'Status' page to view the firmware version. Alternatively, query the device via SNMP using OID 1.3.6.1.4.1.21067.1.1.1.1.0 (LOYTEC-specific).
    Affected if The displayed firmware version equals exactly 6.0.1.
  3. Confirm web management interface is network-accessible
    Verify that the LOYTEC device HTTP/HTTPS ports (default 80/443) are reachable from network segments that should not have management access. Use 'curl http://[device-ip]/' or 'nc -zv [device-ip] 80 443' to test accessibility.
    Affected if The web interface is exposed to untrusted networks without firewall restrictions.
  4. Test for password-hash backup file exposure
    Attempt to access common backup file paths via the web interface, such as 'http://[device-ip]/backup/', 'http://[device-ip]/config/', or variations like '../..//etc/passwd' or '../..//flash/backup/pwd.cfg'. Check for files containing hashed passwords in responses.
    Affected if HTTP requests return password hash files or configuration backups containing hashed credentials without authentication.
  5. Check for path traversal vulnerability
    Send HTTP GET requests with path traversal sequences (e.g., '/..//..//etc/shadow', '/..\..\..\windows\system32\config\sam') to the web server root. Compare response codes and content against expected 404 errors.
    Affected if Path traversal attempts return file contents or directory listings instead of access denied errors.

A LOYTEC device running firmware version 6.0.1 with an exposed web management interface that allows unauthenticated access to password-hash backup files is affected by CVE-2015-7906.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate affected devices behind a firewall with strict access controls, apply any available firmware updates from LOYTEC, and rotate all passwords after patching since the password hashes are compromised.

Fix this in L Switch And L Ip Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7906 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7906 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data