CVE-2020-7848
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 · uneditedThe EFM ipTIME C200 IP Camera is affected by a Command Injection vulnerability in /login.cgi?logout=1 script. To exploit this vulnerability, an attacker can send a GET request that executes arbitrary OS commands via cookie value.
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 confidenceCommand injection vulnerability in EFM ipTIME C200 IP Camera allows remote attackers to execute arbitrary OS commands via cookie values in GET requests to /login.cgi?logout=1. The attacker injects malicious commands through the cookie parameter, which are then executed on the underlying operating system with the privileges of the web server.
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.12CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 device modelAccess the IP camera's web interface or check network device inventory to confirm the device is an ipTIME C200 IP Camera. Look for the model identifier in the device status page or network scan results.Affected if The device is NOT an ipTIME C200 IP Camera (different models are not affected by this specific CVE).
-
Determine the firmware versionLog into the camera's web administration interface and navigate to the System or Firmware section to view the installed firmware version. Alternatively, check the device's status page or API endpoint for version information.Affected if The firmware version is exactly 1.0.12 (this is the only affected version listed). Other versions are not affected.
-
Verify the web interface accessibilityAttempt to access the /login.cgi endpoint with the logout=1 parameter (e.g., http://[camera-ip]/login.cgi?logout=1) using a web browser or curl command. Check if the endpoint responds.Affected if The /login.cgi?logout=1 endpoint is accessible on the network and accepts requests.
-
Check network exposureReview firewall rules, NAT configurations, and access control lists to determine if the camera's web interface (port 80/443) is reachable from untrusted networks or the internet.Affected if The device is directly exposed to the internet or untrusted networks without proper network segmentation.
You are affected if you have an ipTIME C200 IP Camera running firmware version 1.0.12 with the web interface accessible on your 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.
From vendor dataApply vendor firmware patch when available; until then, isolate affected devices in a restricted network segment, disable external access, and monitor for suspicious requests to /login.cgi.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7848 — 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-7848 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