V1600d FirmwareOperating system · Vsolcn

CVE-2020-29380

MEDIUM · 5.9 CVSS v3.1 Published 2020-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
An issue was discovered on V-SOL V1600D V2.03.69 and V2.03.57, V1600D4L V1.01.49, V1600D-MINI V1.01.48, V1600G1 V2.0.7 and V1.9.7, and V1600G2 V1.1.4 OLT devices. TELNET is offered by default but SSH is not always available. An attacker can intercept passwords sent in cleartext and conduct a man-in-the-middle attack on the management of the appliance.

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 · high confidence

V-SOL OLT devices have TELNET enabled by default, which transmits passwords and management traffic in cleartext. Since SSH is not consistently available across all firmware versions, attackers on the network path can intercept credentials and perform man-in-the-middle attacks on device management.

MitigationDisable TELNET and enable SSH for management access. If SSH is unavailable in the current firmware, upgrade to a version that supports SSH or implement VPN/out-of-band management for secure administrative access.

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
V1600d FirmwareOperating system
Affected:= 2.03.57= 2.03.69
V1600d4l FirmwareOperating system
Affected:= 1.01.49
V1600d Mini FirmwareOperating system
Affected:= 1.01.48
V1600g1 FirmwareOperating system
Affected:= 1.9.7= 2.0.7
V1600g2 FirmwareOperating system
Affected:= 1.1.4

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 the device model and firmware version
    Access the OLT web interface or CLI and retrieve the device model (V1600d, V1600d4l, V1600d Mini, V1600g1, or V1600g2) and firmware version information from the system status or about page
    Affected if The device is a V-SOL OLT model and the firmware version matches 2.03.57, 2.03.69, 1.01.49, 1.01.48, 1.9.7, 2.0.7, or 1.1.4 from the affected versions list
  2. Check if TELNET service is enabled
    Log into the device CLI or web interface and navigate to the network services or port configuration section. Look for TELNET server settings or port 23 configuration
    Affected if TELNET service is enabled and listening on the device (typically port 23)
  3. Verify if SSH management is available
    Check the device configuration for SSH (secure shell) options under management access settings. Attempt an SSH connection to the device on port 22 if available
    Affected if SSH is not listed as an available option in the firmware, or SSH connectivity fails and TELNET is the only management protocol available
  4. Test for cleartext credential capture
    From a test workstation on the same network segment, use a packet capture tool (such as tcpdump or Wireshark) while authenticizing to the device via TELNET. Inspect the captured packets for plaintext username and password strings
    Affected if TELNET authentication traffic contains readable username and password in plain text rather than encrypted data

A user is affected if they are running one of the listed V-SOL OLT firmware versions and TELNET is currently enabled as a management access method, with SSH unavailable or not consistently supported in that firmware version.

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

Disable TELNET and enable SSH for management access. If SSH is unavailable in the current firmware, upgrade to a version that supports SSH or implement VPN/out-of-band management for secure administrative access.

Fix this in V1600d Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-29380 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