CVE-2017-17105

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 85%CVSS: 9.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Zivif PR115-204-P-RS V2.3.4.2103 and V4.7.4.2121 (and possibly in-between versions) web cameras are vulnerable to unauthenticated, blind remote command injection via CGI scripts used as part of the web interface, as demonstrated by a cgi-bin/iptest.cgi?cmd=iptest.cgi&-time="1504225666237"&-url=$(reboot) request.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
82
EG Risk 82/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation85% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
85%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 19, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Oct 6, 2026
No fix on record yet.
generic

Silas Cutler (p1nk) on X: "Fun note. #LaCaja from @Hackerstrip is my disclosure for CVE-2017-17105, CVE-2017-17106, and CVE-2017-17107." / X

https://twitter.com/silascutler/status/938052460328968192
generic

Full Disclosure: Three exploits for Zivif Web Cameras (may impact others)

http://seclists.org/fulldisclosure/2017/Dec/42
generic

Packet Storm

http://packetstormsecurity.com/files/158120/Zivif-Camera-2.3.4.2103-iptest.cgi-Blind-Remote-Command-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/145386/Zivif-PR115-204-P-RS-2.3.4.2103-Bypass-Command-Injection-Hardcoded-Password.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-07 23:41 UTCEPSS rescore
  2. 2026-10-06 15:11 UTCEPSS rescore
  3. 2026-09-30 09:30 UTCEG score recompute
  4. 2026-09-28 13:45 UTCEPSS rescore
  5. 2026-09-24 13:59 UTCEPSS rescore
  6. 2026-09-18 19:22 UTCEPSS rescore
  7. 2026-09-17 19:22 UTCEPSS rescore
  8. 2026-09-10 09:26 UTCEPSS rescore
  9. 2026-09-07 15:56 UTCEPSS rescore
  10. 2026-09-04 05:01 UTCEPSS rescore
  11. 2026-08-30 19:13 UTCEPSS rescore
  12. 2026-08-28 21:36 UTCEPSS rescore
  13. 2026-08-27 14:20 UTCEPSS rescore
  14. 2026-08-25 13:44 UTCEPSS rescore
  15. 2026-08-24 14:10 UTCEPSS rescore
  16. 2026-08-20 22:50 UTCEPSS rescore
  17. 2026-08-19 16:59 UTCEPSS rescore
  18. 2026-08-16 02:10 UTCEPSS rescore
  19. 2026-08-13 21:56 UTCEPSS rescore
  20. 2026-08-05 19:12 UTCEPSS rescore
  21. 2026-07-28 15:32 UTCEPSS rescore
  22. 2026-07-26 14:51 UTCEPSS rescore
  23. 2026-07-23 01:28 UTCEG score recompute
  24. 2026-07-22 22:07 UTCEG score recompute
  25. 2026-07-22 14:04 UTCEPSS rescore
Show 49 more
  1. 2026-07-21 15:21 UTCEPSS rescore
  2. 2026-07-21 15:21 UTCEPSS rescore
  3. 2026-07-18 10:00 UTCEPSS rescore
  4. 2026-07-15 16:54 UTCEPSS rescore
  5. 2026-07-15 16:54 UTCEPSS rescore
  6. 2026-07-09 19:06 UTCEPSS rescore
  7. 2026-07-05 02:27 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-07-01 15:02 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-17 17:50 UTCEPSS rescore
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-10 22:15 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-06 13:45 UTCEPSS rescore
  22. 2026-06-06 13:45 UTCEPSS rescore
  23. 2026-06-05 22:44 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-05-31 22:28 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-26 13:42 UTCEPSS rescore
  33. 2026-05-26 13:42 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 08:22 UTCGHSA enrichment
  40. 2026-05-20 04:16 UTCGHSA enrichment
  41. 2026-05-20 00:11 UTCGHSA enrichment
  42. 2026-05-19 20:06 UTCGHSA enrichment
  43. 2026-05-19 16:01 UTCGHSA enrichment
  44. 2026-05-19 11:55 UTCGHSA enrichment
  45. 2026-05-19 07:42 UTCGHSA enrichment
  46. 2026-05-19 03:37 UTCGHSA enrichment
  47. 2026-05-18 23:32 UTCEG score recompute
  48. 2026-05-18 21:30 UTCEPSS rescore
  49. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/unix/http/zivif_ipcheck_exec✓ verified
    First seen Sep 1, 2017

    Zivif Camera iptest.cgi Blind Remote Command Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-17105?
CVE-2017-17105 is a critical vulnerability published on December 19, 2017. Zivif PR115-204-P-RS V2.3.4.2103 and V4.7.4.2121 (and possibly in-between versions) web cameras are vulnerable to unauthenticated, blind remote command injection via CGI scripts used as part of the web interface, as demonstrated by a…
When was CVE-2017-17105 disclosed?
CVE-2017-17105 was first published on December 19, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17105 actively exploited?
CVE-2017-17105 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 85% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-17105?
CVE-2017-17105 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-17105?
No fix for CVE-2017-17105 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-17105

Explore →

Is Your Infrastructure Affected by CVE-2017-17105?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs