CVE-2020-15058
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 · uneditedLindy 42633 4-Port USB 2.0 Gigabit Network Server 2.078.000 devices allow an attacker on the same network to elevate privileges because the administrative password can be discovered by sniffing unencrypted UDP traffic.
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 confidenceThe Lindy 42633 4-Port USB 2.0 Gigabit Network Server transmits administrative credentials in plaintext via unencrypted UDP broadcast traffic on the local network. An attacker with packet capture capabilities on the same network segment can sniff this traffic to discover the administrative password and gain full privileged access to the device.
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= 2.078.000CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Lindy 42633Inspect the physical device label or access the device's web interface or administrative console to verify the model number is Lindy 42633 4-Port USB 2.0 Gigabit Network ServerAffected if Device model is Lindy 42633 and firmware version equals 2.078.000
-
Check firmware versionAccess the device administration interface (web GUI or CLI) and navigate to the firmware or system information section to retrieve the installed firmware version numberAffected if Firmware version is exactly 2.078.000
-
Capture UDP broadcast traffic from the deviceUse a packet capture tool (such as Wireshark or tcpdump) on the same network segment to capture outgoing UDP traffic from the device. Filter for broadcast traffic and inspect packet contents for plaintext administrative credentialsAffected if UDP broadcast packets contain plaintext username and password fields for device administration
-
Verify administrative access uses unencrypted protocolsAttempt to access the device administrative interface and check if the protocol is HTTP (not HTTPS) and if management traffic flows over unencrypted UDPAffected if Management interface is accessible over HTTP without TLS encryption and device sends UDP broadcasts containing authentication data
A user is affected if they own a Lindy 42633 device running firmware version 2.078.000 and the device transmits administrative credentials in plaintext via UDP broadcast on the local network.
Generated from the published advisory. Verify against your own configuration.
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 dataIsolate affected devices on a restricted VLAN or dedicated network segment to limit exposure to untrusted users. Monitor for vendor firmware updates that implement encrypted management communication (TLS/HTTPS) and disable default credentials in favor of strong, unique passwords.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-15058 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15058 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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