CVE-2017-20025: Solare Solar-Log Flash Memory privileges management
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Solare Solar-Log 3.5.3-86.
- Severity is disputed: the assigning authority (CNA) scores it 7.3, NVD 9.8.
Low priority for now. Upgrade to Solare Solar-Log 3.5.3-86 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 9, 2022
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-269
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · VulDB
- 7.3
- 2.5 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| solar-log | solar-log 250 firmware | cpe:2.3:o:solar-log:solar-log_250_firmware |
| solar-log | solar-log 250 | cpe:2.3:h:solar-log:solar-log_250 |
| solar-log | solar-log 300 firmware | cpe:2.3:o:solar-log:solar-log_300_firmware |
| solar-log | solar-log 300 | cpe:2.3:h:solar-log:solar-log_300 |
| solar-log | solar-log 500 firmware | cpe:2.3:o:solar-log:solar-log_500_firmware |
| solar-log | solar-log 500 | cpe:2.3:h:solar-log:solar-log_500 |
| solar-log | solar-log 800e firmware | cpe:2.3:o:solar-log:solar-log_800e_firmware |
| solar-log | solar-log 800e | cpe:2.3:h:solar-log:solar-log_800e |
| solar-log | solar-log 1000 firmware | cpe:2.3:o:solar-log:solar-log_1000_firmware |
| solar-log | solar-log 1000 | cpe:2.3:h:solar-log:solar-log_1000 |
| solar-log | solar-log 1000 pm\+ firmware | cpe:2.3:o:solar-log:solar-log_1000_pm\+_firmware |
| solar-log | solar-log 1000 pm\+ | cpe:2.3:h:solar-log:solar-log_1000_pm\+ |
and 4 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
Solare Solar-Log
- 2.8.4-56, 3.5.2-85affected
Affected versions · NVD (16)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- solar-log solar-log 1000 firmware2.8.4-56
- solar-log solar-log 1000 firmware3.5.2-85
- solar-log solar-log 1000 pm+ firmware2.8.4-56
- solar-log solar-log 1000 pm+ firmware3.5.2-85
- solar-log solar-log 1200 firmware2.8.4-56
- solar-log solar-log 1200 firmware3.5.2-85
- solar-log solar-log 2000 firmware2.8.4-56
- solar-log solar-log 2000 firmware3.5.2-85
- solar-log solar-log 250 firmware2.8.4-56
- solar-log solar-log 250 firmware3.5.2-85
- solar-log solar-log 300 firmware2.8.4-56
- solar-log solar-log 300 firmware3.5.2-85
- solar-log solar-log 500 firmware2.8.4-56
- solar-log solar-log 500 firmware3.5.2-85
- solar-log solar-log 800e firmware2.8.4-56
- solar-log solar-log 800e firmware3.5.2-85
Same product
solar-log: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-47767A backdoor in Solar-Log Gateway products allows remote access via web panel gaining super administration privileges to the attacker.39Monitor
- CVE-2017-20023Solare Solar-Log Network Config privileges management39Monitor
- CVE-2017-20021Solare Solar-Log File Upload privileges management39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-20020Jun 9, 2022 · Solare Solar-Log cross-site request forgery35Monitor
- ← EarlierCVE-2017-20022Jun 9, 2022 · Solare Solar-Log information disclosure30Monitor
- ← EarlierCVE-2017-20024Jun 9, 2022 · Solare Solar-Log denial of service30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Solare Solar-Log | 3.5.3-86 · description | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- T. WeberCyberDanube Security Research reported it to Delta Electronics.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.