# CVE-2017-17662: Path traversal in n/a

> Attackers can read arbitrary files on Yawcam devices via directory traversal in the HTTP server, exposing sensitive system information.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f3m9-fjq3-x8h8

## What is CVE-2017-17662?

CVE-2017-17662 is a high-severity path traversal vulnerability in n/a, published on 10 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2017-17662?

It affects 1 product.


Products: Yawcam Yawcam.

## How do I fix CVE-2017-17662?

No fix has been published for CVE-2017-17662 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-17662 being exploited?

There is no known exploitation of CVE-2017-17662 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17662 and fix it if it is affected.

What it is: CVE-2017-17662 is a high-severity path traversal vulnerability in n/a, published on 10 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17662 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-17662/ (Markdown: https://insights.sbomify.com/CVE-2017-17662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-17662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-17662
- OSV: https://osv.dev/vulnerability/CVE-2017-17662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-17662/
Summaries are generated and may contain mistakes; the official description above is the record.