CVE-2021-26614
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 · uneditedius_get.cgi in IpTime C200 camera allows remote code execution. A remote attacker may send a crafted parameters to the exposed vulnerable web service interface which invokes the arbitrary shell command.
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 confidenceCommand injection vulnerability in ius_get.cgi web interface of IpTime C200 network camera allows remote attackers to execute arbitrary shell commands via crafted parameters sent to the exposed web service.
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.060CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is IpTime C200Access the camera's web interface or check the device label/documentation to verify the exact model number is C200Affected if Device is not an IpTime C200 camera
-
Identify installed firmware versionLog into the camera's web administration interface and navigate to the firmware or system information page to view the current firmware version numberAffected if Firmware version is less than 1.060 (e.g., 1.059, 1.05, etc.)
-
Verify ius_get.cgi web interface is accessibleAttempt to access the URL path /ius_get.cgi on the camera's IP address (e.g., http://[camera-ip]/ius_get.cgi) using a web browser or curl commandAffected if The ius_get.cgi endpoint responds or is reachable on the network
-
Check network exposure of the web serviceDetermine if the camera's web interface is exposed to untrusted networks by checking firewall rules, NAT configuration, or network segment placementAffected if The web interface is directly accessible from the internet or an untrusted network segment
The environment is affected if the device is an IpTime C200 camera running firmware version lower than 1.060 with the ius_get.cgi web interface accessible on the 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.
dbcve · scoped1.060
Apply vendor firmware update if available; otherwise restrict network access to the camera's web interface via firewall or place device behind a NAT/segmented network to prevent external exploitation.
C200 Firmware 1.060 or later
- Download the IpTime C200 firmware version 1.060 or later from the official IpTime vendor website
- Log in to the C200 camera's web administration interface
- Navigate to the System or Firmware Upgrade section in the management console
- Upload the firmware file (.bin or .fw) for version 1.060 or later
- Wait for the firmware upload and installation process to complete (do not power off the device)
- After the camera restarts, verify the firmware version has been updated to 1.060 or later
- Confirm that the ius_get.cgi interface is no longer accepting arbitrary shell commands
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26614 — 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-2021-26614 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