CVE-2020-11950
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 · uneditedVIVOTEK Network Cameras before XXXXX-VVTK-2.2002.xx.01x (and before XXXXX-VVTK-0XXXX_Beta2) allows an authenticated user to upload and execute a script (with resultant execution of OS commands). For example, this affects IT9388-HT devices.
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 confidenceVIVOTEK network cameras contain an authenticated arbitrary file upload vulnerability allowing authenticated users to upload malicious scripts and execute OS commands. The vulnerability stems from insufficient validation of uploaded files in the web interface, enabling remote code execution with elevated 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<= 0222g<= 0222g<= 0222g<= 0222g<= 0222g<= 0222g<= 0222g<= 0222gCVSS 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 camera modelAccess the camera web interface or check the device label/documentation to confirm the exact model number (e.g., CC9381-HV, FD9360-H, FD9368-HTV, FD9380-H, FD9388-HTV, IB9360-H, IB9368-HT, IB9380-H)Affected if The camera model matches one of these: CC9381-HV, FD9360-H, FD9368-HTV, FD9380-H, FD9388-HTV, IB9360-H, IB9368-HT, or IB9380-H
-
Check firmware versionLog into the camera web interface and navigate to System > System Information (or similar) to view the firmware version stringAffected if The firmware version is 0222g or earlier (e.g., 0222g, 0219g, etc.)
-
Verify web interface is enabledConfirm the camera HTTP/HTTPS web management interface is accessible and functionalAffected if The web interface is accessible and responds to HTTP/HTTPS requests
-
Check for configured user accountsNavigate to the user management or accounts section in the camera web interface to list existing user accountsAffected if At least one user account is configured with access to the file upload functionality
The environment is affected if the camera model is one of the eight listed models, the firmware version is 0222g or earlier, the web interface is accessible, and at least one authenticated user account exists.
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 dataUpdate affected VIVOTEK camera firmware to the patched version (VVTK-2.2002.xx.01x or later). If immediate patching is not feasible, restrict management interface access to trusted networks via firewall rules and implement strict authentication controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11950 — 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-11950 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