CVE-2022-47767: A backdoor in Solar-Log Gateway products allows remote access via web panel gaining super administration privileges to the attacker.
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.2% (FIRST EPSS); higher than 69.2% 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: n/a n/a 4.2.8.
Low priority for now. Upgrade to n/a n/a 4.2.8 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 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.
- Published
- Jan 26, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-912
Report tools
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.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 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
Same product
solar-log: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-20025Solare Solar-Log Flash Memory privileges management39Monitor
- 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 |
|---|---|---|
| n/a n/a | 4.2.8 · 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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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
Weakness class (CWE)
CWE-912 · Hidden FunctionalityCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.