CVE intelligence and bounded remediation

CVE-2017-9859 — An issue was discovered in SMA Solar Technology products

Critical CVSS 9.8

An issue was discovered in SMA Solar Technology products. The inverters make use of a weak hashing algorithm to encrypt the password for REGISTER requests. This hashing algorithm can be cracked relatively easily. An attacker will likely be able to crack the password using offline crackers. This cracked password can then be used to register at the SMA servers. NOTE: the vendor's position is that "we consider the probability of the success of such manipulation to be extremely low." Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected

Severity
Critical
CVSS
9.8 (3.0)
Published
2017-08-05
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-327

Affected products

  • sma / sunny_boy_3600_firmware
  • sma / sunny_boy_5000_firmware
  • sma / sunny_tripower_core1_firmware
  • sma / sunny_tripower_15000tl_firmware
  • sma / sunny_tripower_20000tl_firmware
  • sma / sunny_tripower_25000tl_firmware

Showing 6 representative product identities from 39 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Cryptography, certificate, signature, and channel validation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
  • Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
  • Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.

Remediate safely

  • Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
  • Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
  • Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.