Sma
18 vulnerabilities.
All published vulnerabilities with a CVE number in Sma products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2024-1890 | Sma Sunny Webbox Firmware: Vulnerability whereby an attacker could send a malicious link to an authenticated operator, which could allow remote attackers to perform a … | 2024-02-26 | 6.4 |
| CVE-2024-1889 | Sma Clcon-10 Firmware: Cross-Site Request Forgery vulnerability in SMA Cluster Controller, affecting version 01.05.01.R. This vulnerability could allow an attacker to … | 2024-02-26 | 8.8 |
| CVE-2021-46416 | Sma Sunny Tripower Firmware: Insecure direct object reference in SUNNY TRIPOWER 5.0 Firmware version 3.10.16.R leads to unauthorized user groups accessing due to insecure … | 2022-04-07 | 8.1 |
| CVE-2019-13529 | Sma Sunny Webbox Firmware: An attacker could send a malicious link to an authenticated operator, which may allow remote attackers to perform actions with the permissions of … | 2019-10-09 | 8.8 |
| CVE-2017-9864 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. An attacker can change the plant time even when not authenticated in any way. This … | 2017-08-05 | 7.5 |
| CVE-2017-9863 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. If a user simultaneously has Sunny Explorer running and visits a malicious host, … | 2017-08-05 | 8.8 |
| CVE-2017-9862 | Sma Sunny Explorer: An issue was discovered in SMA Solar Technology products. When signed into Sunny Explorer with a wrong password, it is possible to create a debug … | 2017-08-05 | 7.5 |
| CVE-2017-9861 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. The SIP implementation does not properly use authentication with encryption: it is … | 2017-08-05 | 9.8 |
| CVE-2017-9860 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. An attacker can use Sunny Explorer or the SMAdata2+ network protocol to update the device … | 2017-08-05 | 9.8 |
| CVE-2017-9859 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. The inverters make use of a weak hashing algorithm to encrypt the password for REGISTER … | 2017-08-05 | 9.8 |
| CVE-2017-9858 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. By sending crafted packets to an inverter and observing the response, active and inactive … | 2017-08-05 | 7.5 |
| CVE-2017-9857 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. The SMAdata2+ communication protocol does not properly use authentication with … | 2017-08-05 | 8.1 |
| CVE-2017-9856 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. Sniffed passwords from SMAdata2+ communication can be decrypted very easily. The … | 2017-08-05 | 3.4 |
| CVE-2017-9855 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. A secondary authentication system is available for Installers called the Grid Guard … | 2017-08-05 | 9.8 |
| CVE-2017-9854 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. By sniffing for specific packets on the localhost, plaintext passwords can be obtained as … | 2017-08-05 | 9.8 |
| CVE-2017-9853 | Sma Sunny Boy 3600 Firmware: An issue was discovered in SMA Solar Technology products. All inverters have a very weak password policy for the user and installer password. No … | 2017-08-05 | 9.8 |
| CVE-2017-9852 | Sma Sunny Boy 3600 Firmware: An Incorrect Password Management issue was discovered in SMA Solar Technology products. Default passwords exist that are rarely changed. User … | 2017-08-05 | 9.8 |
| CVE-2017-9851 | Sma Sunny Explorer: An issue was discovered in SMA Solar Technology products. By sending nonsense data or setting up a TELNET session to the database port of Sunny … | 2017-08-05 | 7.5 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.