CVE-2020-17475
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 · uneditedLack of authentication in the network relays used in MEGVII Koala 2.9.1-c3s allows attackers to grant physical access to anyone by sending packet data to UDP port 5000.
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 confidenceMissing authentication in MEGVII Koala 2.9.1-c3s network relays allows unauthenticated attackers to grant physical access by sending UDP packets to port 5000. This is an authentication bypass vulnerability in the physical access control system.
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.9.1-c3sCVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MEGVII Koala firmware versionAccess the device management interface or check system information to retrieve the installed firmware version. This is typically found in the device settings, system info page, or via CLI command like 'show version' or 'cat /proc/version' if SSH/telnet access is available.Affected if The installed firmware version is exactly 2.9.1-c3s
-
Confirm network relay feature is enabledCheck the device configuration settings for network relay functionality. This may be visible in the web interface under Network Settings, Relay Settings, or similar, or via configuration files if accessible.Affected if Network relay feature is enabled and configured on the device
-
Verify UDP port 5000 is listeningPerform a network port scan on the device using 'nmap -sU -p 5000 <device_ip>' or check with 'netstat -uan | grep 5000' if you have shell access to the device.Affected if UDP port 5000 is open and listening on the network relay interface
-
Check network exposure of UDP port 5000Review firewall rules and network segmentation to determine if UDP port 5000 is accessible from untrusted networks. Use 'iptables -L' or check network ACLs to identify accessible ports.Affected if UDP port 5000 is accessible from networks outside the trusted management segment
A system is affected if it runs MEGVII Koala firmware version 2.9.1-c3s with the network relay feature enabled and UDP port 5000 exposed to untrusted networks.
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 dataImplement authentication requirements for network relay communications and/or restrict network access to UDP port 5000 via firewall rules or network segmentation to prevent unauthorized physical access commands.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17475 — 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-17475 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