CVE-2020-7879
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 · uneditedThis issue was discovered when the ipTIME C200 IP Camera was synchronized with the ipTIME NAS. It is necessary to extract value for ipTIME IP camera because the ipTIME NAS send ans setCookie('[COOKIE]') . The value is transferred to the --header option in wget binary, and there is no validation check. This vulnerability allows remote attackers to execute remote 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 confidenceA command injection vulnerability exists in ipTIME NAS when synchronizing with ipTIME C200 IP Camera. The NAS sets a cookie value via setCookie() and passes it to wget's --header option without any input validation. An attacker can inject arbitrary commands through a malicious cookie value, leading to remote code execution on the affected 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<= 1.0.16CVSS 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.
-
Identify device modelCheck if the device is an ipTIME C200 IP Camera or an ipTIME NAS device. This can be done via the device's web interface, administrative console, or by checking the device label.Affected if The device is an ipTIME C200 IP Camera or ipTIME NAS involved in camera synchronization.
-
Check firmware version on C200 cameraAccess the C200 camera's web interface and navigate to the firmware version information page, typically found under Settings or System > Firmware/Version. Alternatively, check via CLI if SSH/Telnet is enabled.Affected if The firmware version is 1.0.16 or lower.
-
Verify camera-NAS synchronization is configuredLog into the ipTIME NAS administrative interface and check if the C200 IP Camera synchronization feature is enabled. Look for camera addition or sync settings in the NAS management panel.Affected if The synchronization between NAS and C200 camera is enabled and configured.
-
Check for setCookie and wget usageIf CLI access is available, examine the NAS web server configuration or CGI scripts for the setCookie() function calls that pass values to wget --header options. Look for cookie handling code in the camera sync module.Affected if The vulnerable code path involving setCookie() with wget --header is present in the firmware.
The environment is affected if you are running an ipTIME C200 camera with firmware version 1.0.16 or lower and have the NAS-camera synchronization feature enabled.
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 dataApply vendor firmware updates for ipTIME NAS and IP Camera devices. As a compensating control, restrict network access to trusted devices and disable unnecessary camera-NAS synchronization features if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7879 — 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-7879 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