CVE-2020-5758
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 · uneditedGrandstream UCM6200 series firmware version 1.0.20.23 and below is vulnerable to OS command injection via HTTP. An authenticated remote attacker can execute commands as the root user by sending a crafted HTTP GET to the UCM's "Old" HTTPS API.
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 Grandstream UCM6200 series IP PBX firmware versions 1.0.20.23 and below contains an OS command injection vulnerability in the 'Old' HTTPS API endpoint. An authenticated remote attacker can send specially crafted HTTP GET requests to execute arbitrary operating system commands with root privileges.
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<= 1.0.20.23<= 1.0.20.23<= 1.0.20.23CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify the firmware versionLog into the UCM6200 web interface and navigate to System Settings > Upgrade, or access the device via SSH and run 'show ver' or check /proc/version to retrieve the installed firmware versionAffected if The firmware version is 1.0.20.23 or any version lower than 1.0.20.23
-
Confirm the device modelCheck the device label or access the web interface dashboard to confirm the exact model (UCM6202, UCM6204, or UCM6208)Affected if The device is a UCM6202, UCM6204, or UCM6208 running vulnerable firmware
-
Verify the Old HTTPS API endpoint is accessibleAttempt to access the /api endpoint via HTTPS from an authorized network location, or check the web interface under Application > API Settings to see if the legacy/Old API is enabledAffected if The Old HTTPS API endpoint is enabled and reachable over the network
-
Check remote access configurationNavigate to System Settings > Remote Access in the web interface, or inspect firewall rules via the CLI with 'iptables -L' to determine if the device accepts remote authenticated requestsAffected if Remote management or API access is permitted from untrusted networks
The environment is affected if the device is a UCM6202, UCM6204, or UCM6208 running firmware version 1.0.20.23 or below AND the Old HTTPS API endpoint is enabled and accessible to the attacker.
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 dataUpgrade Grandstream UCM6200 firmware to version 1.0.20.24 or higher. If immediate patching is not feasible, restrict network access to the vulnerable 'Old' HTTPS API endpoint using firewall rules or disable the endpoint if functionality permits.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5758 — 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-5758 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