# CVE-2017-20025: Solare Solar-Log Flash Memory privileges management

> Remote attackers can escalate privileges via the Flash Memory component in Solare Solar-Log devices, requiring an upgrade to mitigate.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-pgc3-76c4-r7v7

## What is CVE-2017-20025?

CVE-2017-20025 is a high-severity vulnerability in Solare Solar-Log, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2-85. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Flash Memory. The manipulation leads to privilege escalation. The attack can be launched remotely. Upgrading to version 3.5.3-86 is able to address this issue. It is recommended to upgrade the affected component.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-20025?

It affects 8 products.


Products: Solar-Log Solar-Log 1000 Firmware, Solar-Log Solar-Log 1000 Pm\+ Firmware, Solar-Log Solar-Log 1200 Firmware, Solar-Log Solar-Log 2000 Firmware, Solar-Log Solar-Log 250 Firmware, Solar-Log Solar-Log 300 Firmware, Solar-Log Solar-Log 500 Firmware, Solar-Log Solar-Log 800e Firmware.

## How do I fix CVE-2017-20025?

No fix has been published for CVE-2017-20025 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-20025 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20025 exists.

## Other vulnerabilities in Solare Solar-Log

- [CVE-2022-47767](https://insights.sbomify.com/CVE-2022-47767/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-20022](https://insights.sbomify.com/CVE-2017-20022/): Solare Solar-Log information disclosure (high 7.5)
- [CVE-2017-20021](https://insights.sbomify.com/CVE-2017-20021/): Solare Solar-Log File Upload privileges management (medium 6.5)
- [CVE-2017-20023](https://insights.sbomify.com/CVE-2017-20023/): Solare Solar-Log Network Config privileges management (medium 6.3)
- [CVE-2017-20020](https://insights.sbomify.com/CVE-2017-20020/): Solare Solar-Log cross-site request forgery (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20025 and fix it if it is affected.

What it is: CVE-2017-20025 is a high-severity vulnerability in Solare Solar-Log, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20025 exists.

Affected product: Solare Solar-Log. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-20025/ (Markdown: https://insights.sbomify.com/CVE-2017-20025/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-20025
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-20025
- OSV: https://osv.dev/vulnerability/CVE-2017-20025

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-20025/
Summaries are generated and may contain mistakes; the official description above is the record.