CVE-2020-11949
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 · uneditedtestserver.cgi of the web service on VIVOTEK Network Cameras before XXXXX-VVTK-2.2002.xx.01x (and before XXXXX-VVTK-0XXXX_Beta2) allows an authenticated user to obtain arbitrary files from a camera's local filesystem. 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 · high confidenceLocal File Inclusion (LFI) vulnerability in testserver.cgi of the VIVOTEK camera web service allows authenticated users to read arbitrary files from the device's filesystem via path traversal. The vulnerability affects IT9388-HT and other VIVOTEK camera models running firmware versions prior to the patched releases.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 and look for the model name in the system information page, or query the device via SNMP or UPnP discovery.Affected if The camera model is one of: CC9381-HV, FD9360-H, FD9368-HTV, FD9380-H, FD9388-HTV, IB9360-H, IB9368-HT, or IB9380-H.
-
Check installed firmware versionIn the camera web interface, navigate to Setup > System > Information to view the firmware version, or query the CGI endpoint /cgi-bin/getparam.cgi?modelname or similar.Affected if The firmware version is 0222g or earlier (for example, 0222g, 0219g, etc.).
-
Confirm testserver.cgi existsAttempt to access the endpoint /cgi-bin/testserver.cgi on the camera (may require authentication).Affected if The endpoint returns a response rather than a 404 error.
-
Verify web interface accessibilityCheck if the camera HTTP/HTTPS ports are exposed to the network, and confirm whether authentication is required to access the web interface.Affected if The web interface is accessible from a network segment and testserver.cgi can be reached after authentication.
A user is affected if their camera model is one of the listed VIVOTEK models AND the firmware version is 0222g or lower, and the testserver.cgi endpoint is accessible via the web interface.
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-provided firmware updates (VVTK-2.2002.xx.01x or later, or VVTK-0XXXX_Beta2 or later). If immediate patching is not feasible, restrict network access to the camera web interface and enforce strong authentication credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11949 — 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-11949 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