Skip to content
Noroxi
CVE-2022-47767· NVD / CVE Program· CNA mitre

A backdoor in Solar-Log Gateway products allows remote access via web panel gaining super administration privileges to the attacker.

A backdoor in Solar-Log Gateway products allows remote access via web panel gaining super administration privileges to the attacker. This affects Solar-Log devices that use firmware version v4.2.7 up to v5.1.1 (included). This does not exist in SL 200, 500, 1000 / fixed in 4.2.8 for SL 250, 300, 1200, 2000, SL 50 Gateway / fixed in 5.1.2 / 6.0.0 for SL Base.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jan 26, 2023
Updated
Jun 17, 2026
EPSS
1.2% · 68th 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.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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

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 6 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 firmwarebefore 4.2.8_117
  • solar-log solar-log 1000 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 1000 pm+ firmwarebefore 4.2.8_117
  • solar-log solar-log 1000 pm+ firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 1200 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 1200 firmwarebefore 4.2.8_117
  • solar-log solar-log 2000 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 2000 firmwarebefore 4.2.8_117
  • solar-log solar-log 250 firmwarebefore 4.2.8_117
  • solar-log solar-log 250 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 300 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 300 firmwarebefore 4.2.8_117
  • solar-log solar-log 50 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 50 firmwarebefore 4.2.8_117
  • solar-log solar-log 500 firmware5.0.0 and later · before 5.1.2_156
  • solar-log solar-log 500 firmwarebefore 4.2.8_117
  • solar-log solar-log 800e firmwarebefore 4.2.8_117
  • solar-log solar-log 800e firmware5.0.0 and later · before 5.1.2_156

Other highest-scoring records for the same primary product.

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
n/a n/a4.2.8 · 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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

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

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

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.

All records