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

> Remote attackers can read sensitive configuration settings from Tiandy IP cameras via a crafted request to TCP port 3001.

- **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:** 11 Oct 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5mj8-9833-w3h6

## What is CVE-2017-15236?

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

### Official description

Tiandy IP cameras 5.56.17.120 do not properly restrict a certain proprietary protocol, which allows remote attackers to read settings via a crafted request to TCP port 3001, as demonstrated by config* files and extendword.txt.

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

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

It affects 1 product.


Products: Tiandy Tiandy Ip Camera Firmware.

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

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

## Is CVE-2017-15236 being exploited?

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

Public exploit code:

- Tiandy IP Cameras 5.56.17.120 - Sensitive Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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