Skip to content
Noroxi
CVE-2017-20025· NVD / CVE Program· CNA VulDB

Solare Solar-Log Flash Memory privileges management

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jun 9, 2022
Updated
Jun 16, 2026
EPSS
1.1% · 64th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.1%

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.

Affected systems

VendorProduct
solar-logsolar-log 250 firmware
solar-logsolar-log 250
solar-logsolar-log 300 firmware
solar-logsolar-log 300
solar-logsolar-log 500 firmware
solar-logsolar-log 500
solar-logsolar-log 800e firmware
solar-logsolar-log 800e
solar-logsolar-log 1000 firmware
solar-logsolar-log 1000
solar-logsolar-log 1000 pm\+ firmware
solar-logsolar-log 1000 pm\+

and 4 more

Affected versions

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

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

Same product

solar-log: all records

Other 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 management
    39Monitor
  • CVE-2017-20021Solare Solar-Log File Upload privileges management
    39Monitor
  • CVE-2017-20020Solare Solar-Log cross-site request forgery
    35Monitor
  • CVE-2017-20024Solare Solar-Log denial of service
    30Monitor
  • CVE-2017-20022Solare Solar-Log information disclosure
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Solare Solar-Log3.5.3-86 · descriptionVendor (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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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 Management

CVSS 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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - 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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

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.

All records