No exploitation reported

CVE-2017-9860

No exploitation reported by the sources we read.

Published2017-08-05
WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

An issue was discovered in SMA Solar Technology products. An attacker can use Sunny Explorer or the SMAdata2+ network protocol to update the device firmware without ever having to authenticate. If an attacker is able to create a custom firmware version that is accepted by the inverter, the inverter is compromised completely. This allows the attacker to do nearly anything: for example, giving access to the local OS, creating a botnet, using the inverters as a stepping stone into companies, etc. NOTE: the vendor reports that this attack has always been blocked by "a final integrity and compatibility check." Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected

Timeline

dates in UTC

2017-08-0517:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-9860?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-9860?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Sma sunny boy 1.5 firmwareversion to verify

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

Sma sunny boy 2.5 firmwareversion to verify

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

Sma sunny boy 3.0 firmwareversion to verify

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

36 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.09.8read 2026-10-23
NVDCVSS 2.010read 2026-10-23
NVDweakness (CWE)CWE-287read 2026-10-23
FIRST EPSSEPSS score2.2 %2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2017-08-05
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-9860?

Is CVE-2017-9860 actively exploited?

Active exploitation of CVE-2017-9860 has not been confirmed. Its EPSS score was 2.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-9860?

CVE-2017-9860 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database