dbcve.org
Cc8160 FirmwareOperating system · Vivotek

CVE-2024-7440

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Vivotek CC8160 VVTK-0100d. It has been classified as critical. This affects the function getenv of the file upload_file.cgi. The manipulation of the argument QUERY_STRING leads to command injection. It is possible to initiate the attack remotely. The identifier VDB-273525 was assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed that the affected release tree is end-of-life.

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 confidence

Command injection vulnerability in Vivotek CC8160 VVTK-0100d camera's upload_file.cgi. The getenv function improperly handles the QUERY_STRING parameter, allowing remote attackers to inject and execute arbitrary shell commands on the device. This is a pre-authentication flaw requiring no credentials.

MitigationDevice is End-of-Life with no vendor patch available. Replace with supported hardware or isolate device on restricted network VLAN with firewall rules blocking external access to CGI endpoints. Monitor for indicators of compromise.

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
Cc8160 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the camera's web interface or use network discovery (e.g., nmap, ONVIF scan) to retrieve the model number. Look for 'CC8160' or 'VVTK-0100d' in the device information.
    Affected if Device model is Vivotek CC8160 with model identifier VVTK-0100d
  2. Confirm firmware version
    Log into the camera web interface and navigate to System > System Information or check the firmware version via SNMP (OID 1.3.6.1.4.1.35760.1.1.1). Compare the version string against vendor release notes.
    Affected if Any firmware version is installed on the CC8160 (all versions are affected)
  3. Verify CGI endpoint accessibility
    Attempt to access the /cgi-bin/upload_file.cgi endpoint from the network. Use a tool like curl: curl -v http://<camera-ip>/cgi-bin/upload_file.cgi
    Affected if The camera responds to requests at /cgi-bin/upload_file.cgi (the endpoint is enabled by default)
  4. Check network exposure
    Review firewall rules and network configuration to determine if the camera's HTTP/HTTPS ports (typically 80/443) are accessible from untrusted networks or the internet.
    Affected if Port 80/443 or CGI endpoints are reachable from external/untrusted networks

If the device is a Vivotek CC8160 (any firmware version) with accessible CGI endpoints, the environment is affected by this pre-authentication command injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Device is End-of-Life with no vendor patch available. Replace with supported hardware or isolate device on restricted network VLAN with firewall rules blocking external access to CGI endpoints. Monitor for indicators of compromise.

Recommended fix High confidence
  1. This vulnerability affects Vivotek CC8160 firmware which is end-of-life and no longer supported by the vendor.
  2. No patch or firmware update will be released for this vulnerability.
  3. Replace the affected CC8160 device with a currently supported model from Vivotek or an alternative vendor.
  4. If replacement is not immediately possible, implement network segmentation to isolate the device from untrusted networks.
  5. Place the camera behind a firewall with restrictive access control lists, limiting management access to trusted IP addresses only.
  6. Monitor for any unauthorized access attempts to the device.
Caveat Device replacement required - end-of-life product with no security updates available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cc8160 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7440 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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