dbcve.org
Network Camera Ib8369 FirmwareOperating system · Vivotek

CVE-2017-9829

HIGH · 7.5 CVSS v3.0 Published 2017-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
High EPSS 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
'/cgi-bin/admin/downloadMedias.cgi' of the web service in most of the VIVOTEK Network Cameras is vulnerable, which allows remote attackers to read any file on the camera's Linux filesystem via a crafted HTTP request containing ".." sequences. This vulnerability is already verified on VIVOTEK Network Camera IB8369/FD8164/FD816BA; most others have similar firmware that may be affected.

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

A path traversal vulnerability exists in the /cgi-bin/admin/downloadMedias.cgi CGI script on VIVOTEK network camera web interfaces. The script fails to properly sanitize path traversal sequences ('..'), allowing remote unauthenticated attackers to read arbitrary files from the device's Linux filesystem by crafting HTTP requests containing '../' sequences in the request parameters.

MitigationApply vendor firmware updates from VIVOTEK; if patches are unavailable, isolate affected devices on restricted network segments and block external access to CGI endpoints via firewall rules.

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
Network Camera Ib8369 FirmwareOperating system
Affected:= ib8369-vvtk-0102a
Network Camera Fd8164 FirmwareOperating system
Affected:= fd8164-_vvtk-0200b
Network Camera Fd816ba FirmwareOperating system
Affected:= fd816ba-vvtk-010101.

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

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

  1. Identify the device model
    Access the camera's web interface or use network scanning to determine if the device is a VIVOTEK Network Camera model Ib8369, Fd8164, or Fd816ba. Check the HTTP Server header or the login page for model identification.
    Affected if The device is one of these three VIVOTEK camera models.
  2. Check the installed firmware version
    Log into the camera web interface and navigate to the firmware or system information page, or query the camera's API for version information. Look for the exact firmware string such as 'ib8369-vvtk-0102a', 'fd8164-_vvtk-0200b', or 'fd816ba-vvtk-010101'.
    Affected if The firmware version matches exactly one of the three affected versions listed.
  3. Confirm the CGI script is present
    Send an HTTP GET request to http://<camera-ip>/cgi-bin/admin/downloadMedias.cgi and verify the endpoint responds (even if with an error). Use a tool like curl or a browser to test.
    Affected if The endpoint returns any HTTP response, indicating the script exists and is accessible.
  4. Verify network exposure to untrusted sources
    Review firewall rules, NAT configurations, or ACLs to determine whether the camera's HTTP/HTTPS ports (80/443) are accessible from outside the trusted internal network or from the internet.
    Affected if Port 80 or 443 on the camera is reachable from untrusted networks or the internet.
  5. Inspect access logs for path traversal attempts
    Review the camera's HTTP access logs or any upstream proxy/firewall logs for requests to /cgi-bin/admin/downloadMedias.cgi containing '../' sequences in query parameters.
    Affected if Log entries show requests with '../' patterns targeting this CGI endpoint.

A user is affected if they operate a VIVOTEK Ib8369, Fd8164, or Fd816ba camera on the specific affected firmware versions, with the downloadMedias.cgi endpoint exposed to network attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates from VIVOTEK; if patches are unavailable, isolate affected devices on restricted network segments and block external access to CGI endpoints via firewall rules.

Fix this in Network Camera Ib8369 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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