# CVE-2017-11635: Information disclosure in n/a

> Attackers can access stored video recordings on Wireless IP Camera 360 devices by directly navigating to specific SD card paths.

- **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:** 26 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-644f-fx6f-4895

## What is CVE-2017-11635?

CVE-2017-11635 is a high-severity vulnerability in n/a, published on 26 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Wireless IP Camera 360 devices. Attackers can read recordings by navigating to /mnt/idea0 or /mnt/idea1 on the SD memory card.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: - Wireless Ip Camera 360.

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

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

## Is CVE-2017-11635 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11632](https://insights.sbomify.com/CVE-2017-11632/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-11634](https://insights.sbomify.com/CVE-2017-11634/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-11633](https://insights.sbomify.com/CVE-2017-11633/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11635 is a high-severity vulnerability in n/a, published on 26 Feb 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-11635 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-11635/ (Markdown: https://insights.sbomify.com/CVE-2017-11635/index.md)
```

## Sources

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

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