# CVE-2017-9863: Cross-site request forgery in n/a

> Cross-site request forgery allows attackers to change inverter settings and compromise devices if users visit malicious sites while using Sunny Explorer.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3v66-3586-p5rh

## What is CVE-2017-9863?

CVE-2017-9863 is a high-severity vulnerability in n/a, published on 5 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in SMA Solar Technology products. If a user simultaneously has Sunny Explorer running and visits a malicious host, cross-site request forgery can be used to change settings in the inverters (for example, issuing a POST request to change the user password). All Sunny Explorer settings available to the authenticated user are also available to the attacker. (In some cases, this also includes changing settings that the user has no access to.) This may result in complete compromise of the device. NOTE: the vendor reports that exploitation is unlikely because Sunny Explorer is used only rarely. Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 40 products.


Products: Sma Sunny Boy 1.5 Firmware, Sma Sunny Boy 2.5 Firmware, Sma Sunny Boy 3.0 Firmware, Sma Sunny Boy 3.6 Firmware, Sma Sunny Boy 3000tl Firmware, Sma Sunny Boy 3600 Firmware, Sma Sunny Boy 3600tl Firmware, Sma Sunny Boy 4.0 Firmware, Sma Sunny Boy 4000tl Firmware, Sma Sunny Boy 5.0 Firmware, Sma Sunny Boy 5000 Firmware, Sma Sunny Boy 5000tl Firmware, Sma Sunny Boy Storage 2.5 Firmware, Sma Sunny Central 1000cp Xt Firmware, Sma Sunny Central 2200 Firmware, Sma Sunny Central 500cp Xt Firmware, Sma Sunny Central 630cp Xt Firmware, Sma Sunny Central 720cp Xt Firmware, Sma Sunny Central 760cp Xt Firmware, Sma Sunny Central 800cp Xt Firmware and 20 more.

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

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

## Is CVE-2017-9863 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9852](https://insights.sbomify.com/CVE-2017-9852/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-9853](https://insights.sbomify.com/CVE-2017-9853/): Weak cryptography in n/a (critical 9.8)
- [CVE-2017-9854](https://insights.sbomify.com/CVE-2017-9854/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-9855](https://insights.sbomify.com/CVE-2017-9855/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-9859](https://insights.sbomify.com/CVE-2017-9859/): Weak cryptography in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9863 is a high-severity vulnerability in n/a, published on 5 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9863 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-9863/ (Markdown: https://insights.sbomify.com/CVE-2017-9863/index.md)
```

## Sources

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

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