# CVE-2017-9857: Missing authorization in n/a

> Attackers can bypass authentication and modify settings on SMA solar inverters via packet injection or replay attacks due to lack of encryption.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-48px-gfg6-r8pv

## What is CVE-2017-9857?

CVE-2017-9857 is a high-severity missing authorization vulnerability in n/a, published on 5 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SMA Solar Technology products. The SMAdata2+ communication protocol does not properly use authentication with encryption: it is vulnerable to man in the middle, packet injection, and replay attacks. Any setting change, authentication packet, scouting packet, etc. can be replayed, injected, or used for a man in the middle session. All functionalities available in Sunny Explorer can effectively be done from anywhere within the network as long as an attacker gets the packet setup correctly. This includes the authentication process for all (including hidden) access levels and the changing of settings in accordance with the gained access rights. Furthermore, because the SMAdata2+ communication channel is unencrypted, an attacker capable of understanding the protocol can eavesdrop on communications. NOTE: the vendor's position is that authentication with encryption is not required on an isolated subnetwork. Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected

Weakness: CWE-287 (Improper Authentication)

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

It affects 39 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 19 more.

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

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

## Is CVE-2017-9857 being exploited?

There is no known exploitation of CVE-2017-9857 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-9857 and fix it if it is affected.

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

## Sources

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

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