CVE-2017-20022
Last modified
CVE-2017-20022 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. A vulnerability has been found in Solare Solar-Log 2.8.4-56/3.5.2-85 and classified as problematic. This vulnerability affects unknown code. EPSS estimates a 1.30% chance of exploitation in the next 30 days.
Description
A vulnerability has been found in Solare Solar-Log 2.8.4-56/3.5.2-85 and classified as problematic. This vulnerability affects unknown code. The manipulation leads to information disclosure. The attack can be initiated remotely. Upgrading to version 3.5.3-86 is able to address this issue. It is recommended to upgrade the affected component.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Solar-Log | Solar-Log 250 Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 250 Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 300 Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 300 Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 500 Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 500 Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 800e Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 800e Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 1000 Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 1000 Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 1000 Pm\+ Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 1000 Pm\+ Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 1200 Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 1200 Firmware | 3.5.2-85 |
| Solar-Log | Solar-Log 2000 Firmware | 2.8.4-56 |
| Solar-Log | Solar-Log 2000 Firmware | 3.5.2-85 |
References
- http://seclists.org/fulldisclosure/2017/Mar/58Exploit, Mailing List, Third Party Advisory
- https://vuldb.com/?id.98932Third Party Advisory
- http://seclists.org/fulldisclosure/2017/Mar/58Exploit, Mailing List, Third Party Advisory
- https://vuldb.com/?id.98932Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-20022?
How severe is CVE-2017-20022?
How do I fix CVE-2017-20022?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-20017A vulnerability, which was classified as critical, has been …8.8
- CVE-2017-20018A vulnerability was found in XAMPP 7.1.1-0-VC14. It has been…7.8
- CVE-2017-20019A vulnerability classified as problematic was found in Solar…7.5
- CVE-2017-2002Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-20020A vulnerability, which was classified as problematic, has be…8.8
- CVE-2017-20021A vulnerability, which was classified as critical, was found…9.8
- CVE-2017-20023A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2…9.8
- CVE-2017-20024A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2…7.5
- CVE-2017-20025A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2…9.8
- CVE-2017-20026A vulnerability has been found in HumHub up to 1.0.1 and cla…6.1
- CVE-2017-20027A vulnerability was found in HumHub up to 1.0.1 and classifi…6.1
- CVE-2017-20028A vulnerability was found in HumHub 0.20.1/1.0.0-beta.3. It …9.8
Are you affected by CVE-2017-20022?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
