CVE intelligence and bounded remediation
CVE-2017-17662 — Yawcam Yawcam security vulnerability
Directory traversal in the HTTP server on Yawcam 0.2.6 through 0.6.0 devices allows attackers to read arbitrary files through a sequence of the form '.x./' or '....\x/' where x is a pattern composed of one or more (zero or more for the second pattern) of either \ or ..\ -- for example a '.\./', '....\/' or '...\./' sequence. For files with no extension, a single dot needs to be appended to ensure the HTTP server does not alter the request, e.g., a "GET /.\./.\./.\./.\./.\./.\./.\./windows/system32/drivers/etc/hosts." request.
- Severity
- High
- CVSS
- 7.5 (3.0)
- Published
- 2018-01-10
- CISA KEV
- Not currently listed
- Ecosystem
- windows/system
- Weaknesses
- CWE-22
Affected products
- yawcam / yawcam
Matched remediation archetype
Path traversal, unsafe upload, and file handling
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace untrusted filenames, archive entries, URLs, and path segments into read, write, include, extraction, and upload operations.
- Identify filesystem roots, mount permissions, symbolic-link behavior, archive handling, and whether uploaded content is web-accessible or executable.
- Review canonicalization and containment checks across supported operating systems and storage backends.
Remediate safely
- Generate server-side storage identifiers and resolve paths beneath a fixed root using filesystem-aware containment checks.
- Reject absolute, parent-relative, alternate-separator, device, link, and archive entries that escape the intended root.
- Store uploads outside executable or served paths, validate type and size, and use private atomic temporary files.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.