# CVE-2016-0870: Information disclosure in n/a

> Remote attackers can read sensitive configuration files from the Trane Tracer SC web server via direct requests.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 19 Sep 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jx26-qvw7-m788

## What is CVE-2016-0870?

CVE-2016-0870 is a medium-severity vulnerability in n/a, published on 19 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web server in Trane Tracer SC 4.2.1134 and earlier allows remote attackers to read sensitive configuration files via a direct request.

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

## Which versions are affected by CVE-2016-0870?

It affects 1 product.


Products: Trane Tracer Sc.

## How do I fix CVE-2016-0870?

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

## Is CVE-2016-0870 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4526](https://insights.sbomify.com/CVE-2016-4526/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0870 and fix it if it is affected.

What it is: CVE-2016-0870 is a medium-severity vulnerability in n/a, published on 19 Sep 2016. 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-2016-0870 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-2016-0870/ (Markdown: https://insights.sbomify.com/CVE-2016-0870/index.md)
```

## Sources

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

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