CVE-2017-2736
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 · uneditedVCM5010 with software versions earlier before V100R002C50SPC100 has a command injection vulnerability. This is due to insufficient validation of user's input. An authenticated attacker could launch a command injection attack.
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 confidenceThe VCM5010 device running software versions prior to V100R002C50SPC100 contains a command injection vulnerability stemming from insufficient validation of user input. An authenticated attacker can exploit this by injecting malicious commands through unsanitized input fields, potentially executing arbitrary commands on the underlying 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< v100r002c50spc100CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 VCM5010 firmware versionAccess the device management interface (web-based or CLI) and navigate to the system information or firmware version section. On the web interface, this is typically found under 'System' > 'Device Information' or 'Maintenance' > 'System Status'. Via CLI, use 'display version' or 'show system-info' if available.Affected if The displayed firmware version is any version prior to V100R002C50SPC100 (for example, V100R002C50SPC050, V100R002C00, or older releases).
-
Confirm the exact version stringRecord the full firmware version string exactly as displayed on the device. Look for version identifiers that include 'V100R002' followed by a build number. Compare this to the affected version range.Affected if The version string begins with V100R002 and the numeric build/code after 'C50SPC' is less than 100 (such as C50SPC050, C50SPC080, or C50SPC099).
-
Determine if web management interface is accessibleAttempt to access the device's web interface via HTTPS or HTTP on the management IP address. The command injection flaw is exploited through input fields in the web interface.Affected if The web management interface is reachable and responds with a login page, indicating the web service is enabled.
-
Check authentication statusReview whether default or weak credentials are in use for the device's web management interface. Attempt to log in with standard default credentials (consult device documentation for defaults) or verify if an existing administrative account exists.Affected if An authenticated session can be established with the device, as the vulnerability requires an authenticated attacker to inject commands through input fields.
The device is affected if the installed firmware version is below V100R002C50SPC100 and the web management interface is accessible with valid credentials.
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 the VCM5010 firmware to version V100R002C50SPC100 or later, which contains the security patch for this vulnerability. Additionally, implement proper input validation and sanitization on all user-supplied data before passing it to system command execution functions.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2736 — 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-2017-2736 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