dbcve.org
V1600d FirmwareOperating system · Vsolcn

CVE-2020-29381

CRITICAL · 9.8 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 →
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
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. Command injection can occur in "upload tftp syslog" and "upload tftp configuration" in the CLI via a crafted filename.

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

OS command injection vulnerability in V-SOL OLT devices (V1600D, V1600D4L, V1600D-MINI, V1600G1, V1600G2) allows remote attackers to execute arbitrary commands via crafted filenames in the 'upload tftp syslog' and 'upload tftp configuration' CLI commands. User-supplied input is not properly sanitized before being passed to the underlying system shell.

MitigationApply vendor-supplied firmware patches if available; otherwise, restrict network access to the device CLI and disable TFTP functionality to reduce attack surface.

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

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

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 V-SOL OLT device model
    Access the device CLI and run 'show version' or check the web interface to identify the exact model (V1600D, V1600D4L, V1600D-MINI, V1600G1, or V1600G2)
    Affected if Device is one of these five models in the affected product list
  2. Determine the firmware version
    Run 'show version' in the CLI or check the system information page in the web interface to obtain the exact firmware version
    Affected if Firmware version is 2.03.57 or 2.03.69 for V1600D; 1.01.49 for V1600D4L; 1.01.48 for V1600D-MINI; 1.9.7 or 2.0.7 for V1600G1; or 1.1.4 for V1600G2
  3. Verify TFTP functionality is accessible
    Attempt to access or list the 'upload tftp syslog' or 'upload tftp configuration' CLI commands, or check if TFTP is enabled in the device configuration
    Affected if TFTP upload commands are available and accessible to the user

You are affected if you have a V-SOL V1600 series OLT device running one of the listed firmware versions and the TFTP upload feature is enabled and accessible in the CLI.

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

Apply vendor-supplied firmware patches if available; otherwise, restrict network access to the device CLI and disable TFTP functionality to reduce attack surface.

Fix this in V1600d Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-29381 — 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-2020-29381 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