An issue was discovered in SMA Solar Technology products.
An issue was discovered in SMA Solar Technology products. Sniffed passwords from SMAdata2+ communication can be decrypted very easily. The passwords are "encrypted" using a very simple encryption algorithm. This enables an attacker to find the plaintext passwords and authenticate to the device. NOTE: the vendor reports that only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected
- Published
- Aug 5, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 50th percentile
- CWE
- CWE-256
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
13
Monitor
Low priority for now.
- CVSS
- 13 / 40 · 3.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| sma | sunny boy 3600 firmware | cpe:2.3:o:sma:sunny_boy_3600_firmware |
| sma | sunny boy 3600 | cpe:2.3:h:sma:sunny_boy_3600 |
| sma | sunny boy 5000 firmware | cpe:2.3:o:sma:sunny_boy_5000_firmware |
| sma | sunny boy 5000 | cpe:2.3:h:sma:sunny_boy_5000 |
| sma | sunny tripower core1 firmware | cpe:2.3:o:sma:sunny_tripower_core1_firmware |
| sma | sunny tripower core1 | cpe:2.3:h:sma:sunny_tripower_core1 |
| sma | sunny tripower 15000tl firmware | cpe:2.3:o:sma:sunny_tripower_15000tl_firmware |
| sma | sunny tripower 15000tl | cpe:2.3:h:sma:sunny_tripower_15000tl |
| sma | sunny tripower 20000tl firmware | cpe:2.3:o:sma:sunny_tripower_20000tl_firmware |
| sma | sunny tripower 20000tl | cpe:2.3:h:sma:sunny_tripower_20000tl |
| sma | sunny tripower 25000tl firmware | cpe:2.3:o:sma:sunny_tripower_25000tl_firmware |
| sma | sunny tripower 25000tl | cpe:2.3:h:sma:sunny_tripower_25000tl |
and 66 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sma sunny boy 1.5 firmwareall versions
- sma sunny boy 2.5 firmwareall versions
- sma sunny boy 3.0 firmwareall versions
- sma sunny boy 3.6 firmwareall versions
- sma sunny boy 3000tl firmwareall versions
- sma sunny boy 3600 firmwareall versions
- sma sunny boy 3600tl firmwareall versions
- sma sunny boy 4.0 firmwareall versions
- sma sunny boy 4000tl firmwareall versions
- sma sunny boy 5.0 firmwareall versions
- sma sunny boy 5000 firmwareall versions
- sma sunny boy 5000tl firmwareall versions
- sma sunny boy storage 2.5 firmwareall versions
- sma sunny central 1000cp xt firmwareall versions
- sma sunny central 2200 firmwareall versions
- sma sunny central 500cp xt firmwareall versions
- sma sunny central 630cp xt firmwareall versions
- sma sunny central 720cp xt firmwareall versions
- sma sunny central 760cp xt firmwareall versions
- sma sunny central 800cp xt firmwareall versions
Same product
sma: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-9860An issue was discovered in SMA Solar Technology products.40Plan
- CVE-2017-9853An issue was discovered in SMA Solar Technology products.40Plan
- CVE-2017-9852An Incorrect Password Management issue was discovered in SMA Solar Technology products.40Plan
- CVE-2017-9861An issue was discovered in SMA Solar Technology products.39Monitor
- CVE-2017-9859An issue was discovered in SMA Solar Technology products.39Monitor
- CVE-2017-9855An issue was discovered in SMA Solar Technology products.39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-256 · Plaintext Storage of a PasswordCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.sma.de/en/statement-on-cyber-security.html
- www.sma.de/fileadmin/content/global/specials/documents/cyber-security/Whitepaper-Cyber-Security-AEN1732_07.pdf
- horusscenario.com/CVE-information/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.