# CVE-2015-6469: Information disclosure in n/a

> Remote attackers can discover script source code in IBC Solar and Danfoss solar controllers, exposing internal logic.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3g92-r6cp-xjxj

## What is CVE-2015-6469?

CVE-2015-6469 is a medium-severity vulnerability in n/a, published on 25 Sep 2015. It can be exploited over the network, with no action from the victim.

### Official description

The interpreter in IBC Solar ServeMaster TLP+ and Danfoss TLX Pro+ allows remote attackers to discover script source code via unspecified vectors.

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

## Which versions are affected by CVE-2015-6469?

It affects 2 products.


Products: Ibc Solar Danfoss Tlx Pro\+, Ibc Solar Servemaster Tlp\+.

## How do I fix CVE-2015-6469?

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

## Is CVE-2015-6469 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6474](https://insights.sbomify.com/CVE-2015-6474/): Information disclosure in n/a (medium 5.0)
- [CVE-2015-6475](https://insights.sbomify.com/CVE-2015-6475/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6469 and fix it if it is affected.

What it is: CVE-2015-6469 is a medium-severity vulnerability in n/a, published on 25 Sep 2015. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6469 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-2015-6469/ (Markdown: https://insights.sbomify.com/CVE-2015-6469/index.md)
```

## Sources

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

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