# CVE-2017-9852: Hardcoded credentials in n/a

> Attackers can exploit hardcoded default and hidden user passwords to gain unauthorized access to SMA Solar Technology inverters.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/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-2fg4-v4xr-h42m

## What is CVE-2017-9852?

CVE-2017-9852 is a critical 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 Incorrect Password Management issue was discovered in SMA Solar Technology products. Default passwords exist that are rarely changed. User passwords will almost always be default. Installer passwords are expected to be default or similar across installations installed by the same company (but are sometimes changed). Hidden user accounts have (at least in some cases, though more research is required to test this for all hidden user accounts) a fixed password for all devices; it can never be changed by a user. Other vulnerabilities exist that allow an attacker to get the passwords of these hidden user accounts. NOTE: the vendor reports that it has no influence on the allocation of passwords, and that global hardcoded master passwords do not exist. Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

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-9852?

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

## Is CVE-2017-9852 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2017-9860](https://insights.sbomify.com/CVE-2017-9860/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9852 is a critical 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-9852 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-9852/ (Markdown: https://insights.sbomify.com/CVE-2017-9852/index.md)
```

## Sources

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

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