dbcve.org
Ib8367a FirmwareOperating system · Vivotek

CVE-2024-7443

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 classified as critical has been found in Vivotek IB8367A VVTK-0100b. Affected is the function getenv of the file upload_file.cgi. The manipulation of the argument QUERY_STRING leads to command injection. It is possible to launch the attack remotely. The identifier of this vulnerability is VDB-273528. 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 IB8367A camera firmware (VVTK-0100b) allows remote attackers to execute arbitrary commands via the QUERY_STRING parameter passed to the getenv function in upload_file.cgi.

MitigationReplace the end-of-life device as no vendor patches are available; if immediate replacement is not feasible, isolate the device behind a firewall and implement strict network segmentation to limit exposure.

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
Ib8367a 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 Vivotek IB8367A camera model
    Check the product label on the device or log into the camera web interface and navigate to System > Information to view the model name
    Affected if The model is listed as Vivotek IB8367A or Ib8367a
  2. Check firmware version
    In the camera web interface, go to System > Information to view the firmware version. Alternatively, check the firmware file name if you have firmware files (look for VVTK-0100b in the filename)
    Affected if Firmware version is any version (all versions of this model are affected)
  3. Verify web interface is network accessible
    Attempt to access the camera web interface via HTTP/HTTPS using the camera IP address (e.g., http://[camera-ip]/)
    Affected if The web interface is reachable from network segments that are not trusted or are internet-facing
  4. Confirm upload_file.cgi is present
    Access the CGI endpoint directly by navigating to http://[camera-ip]/cgi-bin/upload_file.cgi or check if the file exists in the web directory structure
    Affected if The upload_file.cgi script is accessible and responds to requests

You are affected if you have a Vivotek IB8367A camera with any firmware version and its web interface is network-accessible, as the command injection in upload_file.cgi can be exploited via the QUERY_STRING parameter.

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

Replace the end-of-life device as no vendor patches are available; if immediate replacement is not feasible, isolate the device behind a firewall and implement strict network segmentation to limit exposure.

Recommended fix High confidence
  1. This vulnerability affects an end-of-life product (Vivotek IB8367A VVTK-0100b) that is no longer supported by the vendor.
  2. The vendor has confirmed the affected release tree is end-of-life and will not receive patches or updates.
  3. No configuration mitigations are available for this command injection vulnerability in the affected CGI component.
  4. Replace the end-of-life device with a currently supported model from Vivotek or an alternative vendor.

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

Fix this in Ib8367a Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7443 — 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-7443 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